mirror of https://github.com/zulip/zulip.git
8da6098631
Attempting to "upgrade" from `main` to 4.x should abort; Django does not prevent running old code against the new database (though it likely errors at runtime), and `./manage.py migrate` from the old version during the "upgrade" does not downgrade the database, since the migrations are entirely missing in that directory, so don't get reversed. Compare the list of applied migrations to the list of on-disk migrations, and abort if there are applied migrations which are not found on disk. Fixes: #19284. |
||
|---|---|---|
| .. | ||
| lib | ||
| nagios | ||
| setup | ||
| README.md | ||
| __init__.py | ||
| get-django-setting | ||
| 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.