paulmataruso/zulip
1
0
Fork 0
mirror of https://github.com/zulip/zulip.git synced 2025-11-18 21:48:30 +00:00
Code Issues Packages Projects Releases Wiki Activity

docs: Document changing EXTERNAL_HOST after backup restoration.

Browse Source 
Fixes #12704.
This commit is contained in:
Tim Abbott
2019-07-03 21:08:58 -07:00
parent dd1a6a97bd
commit e14a40675b
1 changed files with 19 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files

19
docs/production/maintain-secure-upgrade.md
View File

@@ -399,6 +399,25 @@ installation. Then, run as root:
/home/zulip/deployments/current/scripts/setup/restore-backup /path/to/backup /home/zulip/deployments/current/scripts/setup/restore-backup /path/to/backup
``` ```
When that finishes, your Zulip server should be fully operational again.
#### Changing the hostname
It's common when testing backup restoration to restore backups with a
different user-facing hostname than the original server to avoid
disrupting service (e.g. `zuliptest.example.com` rather than
`zulip.example.com`).
If you do so, just like any other time you change the hostname, you'll
need to [update `EXTERNAL_HOST`](../production/settings.html) and then
restart the Zulip server (after backup restoration completes).
Until you do, your Zulip server will think its user-facing hostname is
still `zulip.example.com` and will return HTTP `400 BAD REQUEST`
errors when trying to access it via `zuliptest.example.com`.
#### Inspecting a backup tarball
If you're not sure what versions were in use when a given backup was If you're not sure what versions were in use when a given backup was
created, you can get that information via the files in the backup created, you can get that information via the files in the backup
tarball `postgres-version`, `os-version`, and `zulip-version`. The tarball `postgres-version`, `os-version`, and `zulip-version`. The