mirror of https://github.com/zulip/zulip.git
acc94a5f32
If running on a stand-alone PostgreSQL server, then supervisor does exist -- but `stop-server` is useless, and in fact cannot run because the Zulip directory may not be readable by the `zulip` user. Detect if this is an application front-end server by looking for `/home/zulip/deployments`, and use the stop-server and flush-memcached from there if it exists. The `create-db.sql` and `terminate-psql-sessions` files are still read from the local directory, but those already have precautions from being from a non-world-readable directory, and are more obviously important to keep in sync with the `create-database` script. |
||
|---|---|---|
| .. | ||
| 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.