Don't always need to drop

diff --git a/docs/administration/backup.md b/docs/administration/backup.md
index 10a86c56395b0749885933a6e15689a021b31be3..1d9b82fccb6f42950815a5bb85849652f62eef24 100644 (file)
--- 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.