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. |
||
|---|---|---|
| .. | ||
| apt-repos | ||
| __init__.py | ||
| compare-settings-to-template | ||
| configure-rabbitmq | ||
| create-database | ||
| create-db.sql | ||
| create-pgroonga.sql | ||
| flush-memcached | ||
| generate-rabbitmq-cookie | ||
| generate-self-signed-cert | ||
| generate_secrets.py | ||
| initialize-database | ||
| install | ||
| pgroonga-config | ||
| reindex-textual-data | ||
| restore-backup | ||
| setup-certbot | ||
| sha256-file-to | ||
| sha256-tarball-to | ||
| terminate-psql-sessions | ||
| upgrade-postgresql | ||