mirror of https://github.com/zulip/zulip.git
382261dc72
We stopped using tsearch-extras in Zulip 2.1.0 after Anders figured out how to achieve its goals with native postgres. However, we never did a `DROP EXTENSION` on systems thta had upgraded, which meant that backups created on systems originally installed with Zulip 2.0.x and older, and later upgraded to Zulip 2.1.x, could not be restored on Zulip servers created with a fresh install of Zulip 2.1.x. We can't do this with a normal database migration, because DROP EXTENSION has to be done as the postgres user, so we add some custom migration code in the upgrade-zulip-stage-2 tool. It's safe to run this whenever tsearch_extras.control is installed because: * Zulip is AFAIK the only software that ever used tsearch_extras. * The package was only installed via puppet on production servers configured to run a local Zulip database. * We'll only run this code once per system, because it removes the package and thus the control files. Fixes #13612. |
||
---|---|---|
.. | ||
lib | ||
nagios | ||
setup | ||
README.md | ||
__init__.py | ||
get-django-setting | ||
purge-old-deployments | ||
restart-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.