mirror of https://github.com/zulip/zulip.git
1f68726cb8
If the `postgresql.version` in `/etc/zulip/zulip.conf` is out of date or wrong, upgrading to the actual current version would drop your production database without prompting. While we do document taking a Zulip backup (which includes a database backup) before running `upgrade-postgresql`[^1], not everyone does so, with possibly catastrophic consequences. Do a true end-to-end check of the version in `/etc/zulip/zulip.conf` by asking Django to query the database for its version, checking that against the configured value, and aborting if there is any disagreement. [^1]: https://zulip.readthedocs.io/en/latest/production/upgrade.html#upgrading-postgresql |
||
|---|---|---|
| .. | ||
| lib | ||
| nagios | ||
| setup | ||
| README.md | ||
| __init__.py | ||
| get-django-setting | ||
| log-search | ||
| purge-old-deployments | ||
| refresh-sharding-and-restart | ||
| 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.