logo

pleroma

My custom branche(s) on git.pleroma.social/pleroma/pleroma
commit: 1aabc0672e17c2b931eae19d39da8713f9ff40a0
parent d239bd3ca4348d38c12ab54c7e2e9cb2b825cc3c
Author: feld <feld@feld.me>
Date:   Fri,  9 Oct 2020 16:30:35 +0000

Merge branch 'docs/improve-backup-restore' into 'develop'

Spelling

See merge request pleroma/pleroma!3063

Diffstat:

Mdocs/administration/backup.md2+-
1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/docs/administration/backup.md b/docs/administration/backup.md @@ -17,7 +17,7 @@ 5. Drop the existing database if restoring in-place. `sudo -Hu postgres psql -c 'DROP DATABASE <pleroma_db>;'` 6. Restore the database schema and pleroma postgres role the with the original `setup_db.psql` if you have it: `sudo -Hu postgres psql -f config/setup_db.psql`. - Alernatively, run the `mix pleroma.instance gen` task again. You can ignore most of the questions, but make the database user, name, and password the same as found in your backup of `config/prod.secret.exs`. Then run the restoration of the pleroma role and schema with of the generated `config/setup_db.psql` as instructed above. You may delete the `config/generated_config.exs` file as it is not needed. + Alternatively, run the `mix pleroma.instance gen` task again. You can ignore most of the questions, but make the database user, name, and password the same as found in your backup of `config/prod.secret.exs`. Then run the restoration of the pleroma role and schema with of the generated `config/setup_db.psql` as instructed above. You may delete the `config/generated_config.exs` file as it is not needed. 7. Now restore the Pleroma instance's data into the empty database schema: `sudo -Hu postgres pg_restore -d <pleroma_db> -v -1 </path/to/backup_location/pleroma.pgdump>` 8. If you installed a newer Pleroma version, you should run `mix ecto.migrate`[^1]. This task performs database migrations, if there were any.