Gitea and Vaultwarden both have SQLite databases. We'll need to add some logic to ensure these are in a consistent state before beginning the backup. Fortunately, neither of them are very busy databases, so the likelihood of an issue is pretty low. It's definitely more important to get backups going again sooner, and we can deal with that later.
24 lines
721 B
YAML
24 lines
721 B
YAML
nextcloud_server_name: nextcloud.pyrocufflink.net
|
|
apache_server_name: '{{ nextcloud_server_name }}'
|
|
nextcloud_trusted_proxies:
|
|
- 127.0.0.1
|
|
- ::1
|
|
- '{{ lookup("dig", groups["public-web"][0]) }}'
|
|
nextcloud_trusted_domains:
|
|
- nextcloud.pyrocufflink.net
|
|
- nextcloud.pyrocufflink.blue
|
|
- '{{ ansible_fqdn }}'
|
|
nextcloud_smtp:
|
|
from: nextcloud@pyrocufflink.net
|
|
host: mail.pyrocufflink.blue
|
|
port: 25
|
|
dnf_automatic_exclude: nextcloud
|
|
|
|
nextcloud_db_host: postgresql.pyrocufflink.blue;sslcert=/etc/nextcloud/postgresql.cer;sslkey=/etc/nextcloud/postgresql.key;sslrootcert=system;sslmode=verify-full
|
|
|
|
restic_include:
|
|
- /var/lib/nextcloud
|
|
restic_exclude:
|
|
- /var/lib/nextcloud/data/*/files_trashbin
|
|
- /var/lib/nextcloud/.snapshots
|