mirror of https://github.com/zulip/zulip.git
7187146422
`--no-init-db` is used to silence the need for `--hostname` and `--email` arguments; it is a proxy for "this is not a frontend host." We would ideally like to use `has_class` to know if the user's provided puppet classes are include an `app_frontend`, and thus `--hostname` and `--email` are required -- but doing that requires several other steps, and we would like this feedback to be immediate. We make the presence of `--puppet-classes` equivalent to `--no-init-db`, since nearly every configuration with `--puppet-classes` does not install both a database and a frontend, which is what is required to initialize a database. |
||
---|---|---|
.. | ||
lib | ||
nagios | ||
setup | ||
README.md | ||
__init__.py | ||
get-django-setting | ||
log-search | ||
purge-old-deployments | ||
refresh-sharding-and-restart | ||
reload-clients | ||
restart-server | ||
start-server | ||
stop-server | ||
upgrade-zulip | ||
upgrade-zulip-from-git | ||
zulip-puppet-apply |
README.md
This directory contains scripts that:
-
Generally do not require access to Django or the database (those are "management commands"), and thus are suitable to run operationally.
-
Are useful for managing a production deployment of Zulip (many are also used in a Zulip development environment, though development-only scripts live in
tools/
).
For more details, see https://zulip.readthedocs.io/en/latest/overview/directory-structure.html.