installer: Only set deploy_type = production in zulip.conf.

The value is a holdover from when it controlled runtime behavior,
which it no longer does.

Stop taking a DEPLOYMENT_TYPE, which is unused; the python code only
care about if the option exists, not its value.
This commit is contained in:
Alex Vandiver
2020-06-25 22:11:02 +00:00
committed by Tim Abbott
parent 117d32cd8c
commit 2de8400a32

View File

@@ -81,8 +81,6 @@ fi
read -r -a APT_OPTIONS <<< "${APT_OPTIONS:-}"
# Install additional packages.
read -r -a ADDITIONAL_PACKAGES <<< "${ADDITIONAL_PACKAGES:-}"
# Deployment type is almost always voyager.
DEPLOYMENT_TYPE="${DEPLOYMENT_TYPE:-voyager}"
# Comma-separated list of puppet manifests to install. default is
# zulip::voyager for an all-in-one system or zulip::dockervoyager for
# Docker. Use e.g. zulip::app_frontend for a Zulip frontend server.
@@ -345,7 +343,7 @@ else
cat <<EOF > /etc/zulip/zulip.conf
[machine]
puppet_classes = $PUPPET_CLASSES
deploy_type = $DEPLOYMENT_TYPE
deploy_type = production
[postgresql]
version = $POSTGRES_VERSION