mirror of
https://github.com/zulip/zulip.git
synced 2026-06-30 21:11:04 +08:00
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 |
||
|---|---|---|
| .. | ||
| apt-repos | ||
| __init__.py | ||
| compare-settings-to-template | ||
| configure-rabbitmq | ||
| create-database | ||
| create-db.sql | ||
| create-pgroonga.sql | ||
| flush-memcached | ||
| generate_secrets.py | ||
| generate-rabbitmq-cookie | ||
| generate-self-signed-cert | ||
| initialize-database | ||
| install | ||
| reindex-textual-data | ||
| restore-backup | ||
| setup-certbot | ||
| sha256-file-to | ||
| sha256-tarball-to | ||
| terminate-psql-sessions | ||
| upgrade-postgresql | ||