diff options
| author | Mark Felder <feld@FreeBSD.org> | 2020-10-08 15:54:28 -0500 |
|---|---|---|
| committer | Mark Felder <feld@FreeBSD.org> | 2020-10-08 15:54:28 -0500 |
| commit | 5f38e03c8a487da3e9f7f480a684b0dad6a3c086 (patch) | |
| tree | 7ab1bb93fc7e4266e84893c1686dbff1cb2e64a9 | |
| parent | a02ed3920f43b4dd67737e5989f65f3298546ea0 (diff) | |
| download | pleroma-5f38e03c8a487da3e9f7f480a684b0dad6a3c086.tar.gz | |
Don't always need to drop
| -rw-r--r-- | docs/administration/backup.md | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/docs/administration/backup.md b/docs/administration/backup.md index 10a86c563..1d9b82fcc 100644 --- a/docs/administration/backup.md +++ b/docs/administration/backup.md @@ -14,7 +14,7 @@ 2. Stop the Pleroma service. 3. Go to the working directory of Pleroma (default is `/opt/pleroma`) 4. Copy the above mentioned files back to their original position. -5. Drop the existing database. `sudo -Hu postgres psql -c 'DROP DATABASE <pleroma_db>;` +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 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. |