Ver a proveniência

Update docs/configuring-playbook-backup-borg.md: sync the description with the document for the MASH project

Signed-off-by: Suguru Hirahara <acioustick@noreply.codeberg.org>
pull/4052/head
Suguru Hirahara há 1 ano
ascendente
cometimento
86beae4863
Não foi encontrada uma chave conhecida para esta assinatura, na base de dados ID da chave GPG: E4F9743DAB4B7B75
1 ficheiros alterados com 1 adições e 1 eliminações
  1. +1
    -1
      docs/configuring-playbook-backup-borg.md

+ 1
- 1
docs/configuring-playbook-backup-borg.md Ver ficheiro

@@ -22,7 +22,7 @@ You will need a remote server where BorgBackup will store the backups. There are


### Check the Postgres version ### Check the Postgres version


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.
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 by default.


Unless you disable the Postgres-backup support, make sure that the Postgres version of your homeserver's database is compatible with borgmatic. You can check the compatible versions [here](https://github.com/mother-of-all-self-hosting/ansible-role-backup_borg/blob/main/defaults/main.yml). Unless you disable the Postgres-backup support, make sure that the Postgres version of your homeserver's database is compatible with borgmatic. You can check the compatible versions [here](https://github.com/mother-of-all-self-hosting/ansible-role-backup_borg/blob/main/defaults/main.yml).




Carregando…
Cancelar
Guardar