docs/prod*: Simplify core install instructions a bit by cutting /root/zulip .

This works fine in my testing -- I followed it on a fresh `trusty` VM,
after just getting SSL certs with our LetsEncrypt instructions, and
the install completed successfully.

And in the source tree, the only evidence I can find of a potential
remaining dependency on the `/root/zulip` path is the Nagios config in
`puppet/zulip_ops/`.  That's actually already broken, in that it
depends on `/root/zulip/api/`, so we'll have to sort that out;
and in any case, it doesn't matter to most people installing Zulip.

Add a mention that the install script will move the just-unpacked
directory out from under you.  While we're here, add a few words about
where the deployed code is laid out.

Text of those last words tweaked by tabbott.
This commit is contained in:
Greg Price
2017-08-09 17:36:13 -07:00
committed by Tim Abbott
parent 71fa4dfa5d
commit cd897b7a99

View File

@@ -32,21 +32,19 @@ tarball](https://www.zulip.org/dist/releases/zulip-server-latest.tar.gz)
with the following commands:
```
sudo -i # If not already root
cd /root
cd $(mktemp -d)
wget https://www.zulip.org/dist/releases/zulip-server-latest.tar.gz
rm -rf /root/zulip && mkdir /root/zulip
tar -xf zulip-server-latest.tar.gz --directory=/root/zulip --strip-components=1
tar -xf zulip-server-latest.tar.gz
```
Then, run the Zulip install script:
```
/root/zulip/scripts/setup/install
sudo -s # If not already root
./zulip-server-*/scripts/setup/install
```
This may take a while to run, since it will install a large number of
dependencies. It also creates a `zulip` user, which will be used to run
the various Zulip servers.
dependencies.
The Zulip install script is designed to be idempotent, so if it fails,
you can just rerun it after correcting the issue that caused it to
@@ -54,6 +52,18 @@ fail. Also note that it automatically logs a transcript to
`/var/log/zulip/install.log`; please include a copy of that file in
any bug reports.
The install script does several things:
* Creates `zulip` user, which the various Zulip servers will run as,
* Creates `/home/zulip/deployments/`, which the Zulip code for this
deployment (and future deployments when you upgrade) go into. At the
very end of the install process, the script moves the Zulip code tree
it's running from (which you unpacked from a tarball above) to a
directory there, and makes `/home/zulip/deployments/current` as a
symbolic link to it.
* Installs Zulip's various dependencies.
* Cconfigures the various third-party services Zulip uses, including
Postgres, RabbitMQ, Memcached and Redis.
## Step 3: Configure Zulip
Configure the Zulip server instance by editing `/etc/zulip/settings.py` and