docs: Clarify preparatory process for data import.

You need a Zulip server running the a matching version, and no longer
need to do an upgrade from master before using established import tools.
This commit is contained in:
Tim Abbott 2018-11-14 16:58:34 -08:00
parent 67c3593b39
commit f1c65975ad
4 changed files with 23 additions and 6 deletions

View File

@ -55,6 +55,16 @@ archive of all the organization's uploaded files.
## Import into a new Zulip server ## Import into a new Zulip server
The Zulip server you're importing into needs to be running the same
version of Zulip as the server you exported from, so that the same
formats are consistent. For exports from zulipchat.com, usually this
means you need to upgrade your Zulip server to the latest `master`
branch, using [upgrade-zulip-from-git][upgrade-zulip-from-git].
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).
Log in to a shell on your Zulip server as the `zulip` user. Run the 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 following commands, replacing the filename with the path to your data
export tarball: export tarball:

View File

@ -33,9 +33,10 @@ organization first.
### Import into a self-hosted Zulip server ### Import into a self-hosted Zulip server
Because the import tool is very new, you will need to First
upgrade your Zulip server to the latest `master` branch, [install a new Zulip server](https://zulip.readthedocs.io/en/stable/production/install.html),
using [upgrade-zulip-from-git][upgrade-zulip-from-git]. skipping "Step 3: Create a Zulip organization, and log in" (you'll
create your Zulip organization via the data import tool instead).
Log in to a shell on your Zulip server as the `zulip` user. To import with Log in to a shell on your Zulip server as the `zulip` user. To import with
the most common configuration, run the following commands, replacing the most common configuration, run the following commands, replacing

View File

@ -65,6 +65,11 @@ organization first.
### Import into a self-hosted Zulip server ### Import into a self-hosted Zulip server
First
[install a new Zulip server](https://zulip.readthedocs.io/en/stable/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).
Because the import tool is very new, you will need to Because the import tool is very new, you will need to
upgrade your Zulip server to the latest `master` branch, upgrade your Zulip server to the latest `master` branch,
using [upgrade-zulip-from-git][upgrade-zulip-from-git]. using [upgrade-zulip-from-git][upgrade-zulip-from-git].

View File

@ -35,9 +35,10 @@ organization first.
### Import into a self-hosted Zulip server ### Import into a self-hosted Zulip server
Because the import tool is very new, you will need to First
upgrade your Zulip server to the latest `master` branch, [install a new Zulip server](https://zulip.readthedocs.io/en/stable/production/install.html),
using [upgrade-zulip-from-git][upgrade-zulip-from-git]. skipping "Step 3: Create a Zulip organization, and log in" (you'll
create your Zulip organization via the data import tool instead).
Log in to a shell on your Zulip server as the `zulip` user. To import with Log in to a shell on your Zulip server as the `zulip` user. To import with
the most common configuration, run the following commands, replacing the most common configuration, run the following commands, replacing