From b79ba536225cf00c99488570a6d51effe121a145 Mon Sep 17 00:00:00 2001 From: Suguru Hirahara Date: Sat, 2 Nov 2024 23:52:23 +0900 Subject: [PATCH] Reflect the feedback Signed-off-by: Suguru Hirahara --- docs/configuring-playbook-backup-borg.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/configuring-playbook-backup-borg.md b/docs/configuring-playbook-backup-borg.md index 96a2a8a26..b0bcfe68b 100644 --- a/docs/configuring-playbook-backup-borg.md +++ b/docs/configuring-playbook-backup-borg.md @@ -10,11 +10,11 @@ The backup will run based on `backup_borg_schedule` var (systemd timer calendar) By default, if you're using the integrated Postgres database server (as opposed to [an external Postgres server](configuring-playbook-external-postgres.md)), backups with BorgBackup will also include dumps of your Postgres database. An alternative solution for backing up the Postgres database is [postgres backup](configuring-playbook-postgres-backup.md). If you decide to go with another solution, you can disable Postgres-backup support for BorgBackup using the `backup_borg_postgresql_enabled` variable. -**Note**: the `matrix-backup-borg` role is not managed by this repository but its [own repository](https://github.com/mother-of-all-self-hosting/ansible-role-backup_borg). +**Note**: the component is not managed by this repository but its [own repository](https://github.com/mother-of-all-self-hosting/ansible-role-backup_borg). ## Prerequisites -1. Make sure that the Postgres version of your homeserver's database is compatible with borgmatic. +1. If you do not disable Postgres-backup support, make sure that the Postgres version of your homeserver's database is compatible with borgmatic. 2. Create a new SSH key: