mirror of https://github.com/zulip/zulip.git
2057057be4
This can happen if `machine.pgroonga` is set during initial installation. We cannot run `CREATE EXTENSION PGROONGA` because the database that we need to run that statement in does not exist yet; make the command a silent no-op that does not create the `pgroonga_setup.sql.applied` flag file, such that a later `zulip-puppet-apply` once the database exists can pick up and install the extension. |
||
|---|---|---|
| .. | ||
| lib | ||
| nagios | ||
| setup | ||
| README.md | ||
| __init__.py | ||
| get-django-setting | ||
| log-search | ||
| 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.