mirror of
https://github.com/zulip/zulip.git
synced 2026-06-15 21:01:31 +08:00
304bd86173
Historically, one has needed to build a release tarball in order to use/test the Zulip installer, but you could upgrade a Zulip server from Git. However, the only reason for that requirement was that we didn't run `tools/update-prod-static` as part of the install script if it's required. A good test for that case is whether we're in a Git repository, but a better one is to check whether the prod-static content exists in the tarball paths. Fixes #3704. |
||
|---|---|---|
| .. | ||
| lib | ||
| nagios | ||
| setup | ||
| __init__.py | ||
| clean-unused-caches | ||
| get-django-setting | ||
| purge-old-deployments | ||
| README.md | ||
| restart-server | ||
| upgrade-zulip | ||
| upgrade-zulip-from-git | ||
| zulip-puppet-apply | ||
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 http://zulip.readthedocs.io/en/latest/directory-structure.html.