6 Commits

Author	SHA1	Message	Date
PieterCK	68b3ce482a	check-database-compatibility: Refactor a STALE_MIGRATIONS. ... This consolidates the list of stale migration to `lib/migration_status.py` as `STALE_MIGRATIONS`. This is a prep work to make the migration status tool at `migration_status.py` be able to clean its output of these migrations too.	2025-01-24 17:08:37 -08:00
Anders Kaseorg	2bb87aebec	install: Remove PostgreSQL 12 support. ... PostgreSQL 12 reaches end of life on November 14, 2024. Signed-off-by: Anders Kaseorg <anders@zulip.com>	2024-11-01 15:33:31 -07:00
Anders Kaseorg	ead7b9177a	check-database-compatibility: Ignore twofactor typo. ... Signed-off-by: Anders Kaseorg <anders@zulip.com>	2023-08-23 22:14:26 -07:00
David Rosa	d205850d54	docs: Update .html links pointing to "Upgrade Zulip" or "Modify Zulip". ... Follow-up to #24089.	2023-08-11 16:49:32 -07:00
Alex Vandiver	1accc6929e	upgrade: Check PostgreSQL versions after venv setup. ... The claim in the comment from c8ec3dfcf6, that we can and should use the current deploy's venv, misses one key case -- when upgrading the operating system, the current deploy's venv is unworkable, since it was configured for a previous version of Python. As such, any attempt to load Django to verify the version of PostgreSQL it is talking to must happen after the venv is configured. Move the database version check into `scripts/lib/check-database-compatibility`, which also moves it after the new venv is configured. Because we no longer reliably know, at `apt-get upgrade` time, what version of PostgreSQL is installed, we hold all versions of the pgroonga packages.	2023-07-19 14:19:28 -07:00
Anders Kaseorg	5a79ca251b	check-database-compatibility: Drop .py from script name. ... Signed-off-by: Anders Kaseorg <anders@zulip.com>	2023-03-03 18:02:37 -08:00