install: Fix up success message in `--no-init-db` case.

The installation isn't really complete here, and wasn't even when this
was the only success case; the instructions we're giving are for the
next step in the installation.

These instructions don't say what to do in an actual use case for this
option, but decent instructions there will require having a concrete
use case in front of us and designing the flow for it.  At this stage,
just say where we are in the normal flow, and an admin who's chosen to
go off that flow can figure out how they want to vary it from there.
This commit is contained in:
Greg Price 2018-03-02 16:13:49 -08:00
parent f22712e8e8
commit 678fcef5bd
1 changed files with 3 additions and 7 deletions

View File

@ -281,15 +281,11 @@ if [ -n "$NO_INIT_DB" ]; then
set +x
cat <<EOF
Installation complete!
Success!
Now edit /etc/zulip/settings.py and fill in the mandatory values.
Stopping because --no-init-db was passed. To complete the installation, run:
Once you've done that, please run:
su zulip -c /home/zulip/deployments/current/scripts/setup/initialize-database
To configure the initial database.
su zulip -c /home/zulip/deployments/current/scripts/setup/initialize-database
EOF
exit 0
fi