From d63cf04a200883adb73453208daf698f7338cc1a Mon Sep 17 00:00:00 2001 From: Tim Abbott Date: Sun, 9 Aug 2020 17:44:12 -0700 Subject: [PATCH] docs: Clarify how manage.py backup --output works. --- docs/production/export-and-import.md | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) diff --git a/docs/production/export-and-import.md b/docs/production/export-and-import.md index b507a703521b5..da91db968315e 100644 --- a/docs/production/export-and-import.md +++ b/docs/production/export-and-import.md @@ -65,8 +65,9 @@ su zulip -c '/home/zulip/deployments/current/manage.py backup' ``` The backup tool provides the following options: -- `--output`: Path where the output file should be stored. If no path is - provided, the output file is saved to a temporary directory. +- `--output=/tmp/backup.tar.gz`: Filename to write the backup tarball + to (default: write to a file in `/tmp`). On success, the + console output will show the path to the output tarball. - `--skip-db`: Skip backup of the database. Useful if you're using a remote postgres host with its own backup system and just need to backup non-database state.