mirror of https://github.com/zulip/zulip.git
067196c508
I remove `is_force` from `file_or_package_hash_updated` and modernize its mypy annotations. If `is_force` is `True`, we just now run the thing we want to force-run without having to call `file_or_package_hash_updated` to expensively and riskily return `True`. Another nice outcome of this change is that if `file_or_package_hash_updated` returns `True`, you can know that the file or package has indeed been updated. For the case of `build_pygments_data` we also skip an `os.path.exists` check when `is_force` is `True`. We will short-circuit more logic in the next few commits, as well as cleaning up some of the long/wrapper lines in the `if` statements. |
||
|---|---|---|
| .. | ||
| 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.