paulmataruso/zulip
1
0
Fork 0
mirror of https://github.com/zulip/zulip.git synced 2025-11-04 05:53:43 +00:00
Code Issues Packages Projects Releases Wiki Activity

export: Document /etc/zulip when discussing server migrations.

Browse Source
This commit is contained in:
Tim Abbott
2019-02-02 23:20:19 -08:00
parent afe2197210
commit 001ec76e1f
1 changed files with 15 additions and 6 deletions
Download Patch File Download Diff File Expand all files Collapse all files

21
docs/production/export-and-import.md
View File

@@ -13,12 +13,14 @@ time to time.
If you want to move hardware for a self-hosted Zulip installation, we
recommend Zulip's
[database-level backup and restoration process][backups]. Zulip's
backup process is structurally very unlikely to ever develop bugs, and
will restore your Zulip server to the exact state it was left in. The
big thing it can't do is support a migration to a server hosting a
different set of organizations than the original one (because doing so
generally requires renumbering all the users/messages/etc.).
[database-level backup and restoration process][backups] for a better
experience. Zulip's database-level backup process is faster,
structurally very unlikely to ever develop bugs, and will restore your
Zulip server to the exact state it was left in. The big thing it
can't do is support a migration to a server hosting a different set of
organizations than the original one, e.g. migrations between
self-hosting and Zulip Cloud (because doing so in the general case
requires renumbering all the users/messages/etc.).
Zulip's export/import tools (documented on this page) have full
support for such a renumbering process. While these tools are
@@ -65,6 +67,13 @@ First [install a new Zulip server](../production/install.html),
skipping "Step 3: Create a Zulip organization, and log in" (you'll
create your Zulip organization via the data import tool instead).
If your new Zulip server is meant to fully replace a previous Zulip
server, you may want to copy the contents of `/etc/zulip` to your new
server at this point to reuse the server-level configuration and
secret keys from your old server. See our
[documentation on backups][backups] for details on the contents of
this directory.
Log in to a shell on your Zulip server as the `zulip` user. Run the
following commands, replacing the filename with the path to your data
export tarball: