mirror of
https://github.com/zulip/zulip.git
synced 2025-10-23 16:14:02 +00:00
8ae167dc05
Installs which are upgrading to current `main`, and are upgrading for the very first time from an install which was originally from git, have a `/home/zulip/deployments/current` which, unlike all later upgrades, is not a `git worktree` of `/srv/zulip.git`, but rather a direct `git clone` of some arbitrary URL. As such, it does not have an `upstream` remote, nor a cached `zulip-git-version` file. This makes later attempts to determine the pre-upgrade revision of git (for pre-deploy hooks) fail, as without a `zulip-git-version` file, `ZULIP_VERSION` is insufficiently-specific (e.g. `6.1+git`), and there is no guarantee the necessary tags exist either. While we can make fresh git installs set up an `upstream` and run `./tools/cache-zulip-git-version` going forward (see subsequent commit), that does not address the issue for deploys which already exist. For those, we must configure and fetch a `remote` in the old checkout, followed by re-generating a cached `zulip-git-version`. Fixes: #25076.
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.