zulip/scripts
Greg Price 64c608a51a install: Clarify how we set locale during install, and why.
This updates commit 11ab545f3 "install: Set the locale ..."
to be somewhat cleaner, and to explain more in the commit message.

In some environments, either pip itself fails or some packages fail to
install, and setting the locale to en_US.UTF-8 resolves the issue.

We heard reports of this kind of behavior with at least two different
sets of symptoms, with 1.7.0 or its release candidates:
  https://chat.zulip.org/#narrow/stream/general/subject/Trusty.201.2E7.20Upgrade/near/302214
  https://chat.zulip.org/#narrow/stream/production.20help/subject/1.2E6.20to.201.2E7/near/306250

In all reported cases, commit 11ab545f3 or equivalent fixed the issue.

Setting LC_CTYPE is redundant when also setting LC_ALL, because LC_ALL
overrides all `LC_*` environment variables; so skip that.  Also move
the line in `install` to a more appropriate spot, and adjust the
comments.
2017-11-22 18:11:20 -08:00
..
lib install: Clarify how we set locale during install, and why. 2017-11-22 18:11:20 -08:00
nagios scripts: Replace optparse with argparse. 2017-11-21 21:23:41 -08:00
setup thumbor: Auto generate thumbor_key and add it to zulip settings. 2017-11-16 22:34:14 -08:00
README.md docs: Update links from codebase to point to ReadTheDocs. 2017-11-16 10:53:49 -08:00
__init__.py Factor out venv-creating code from provision.py. 2016-06-21 11:25:41 -07:00
get-django-setting Remove `from __future__ import absolute_import`. 2017-10-17 22:59:42 -07:00
purge-old-deployments caches: Suppress unnecessary output when cleaning caches. 2017-09-25 16:34:03 -07:00
restart-server scripts: Remove import print_function. 2017-09-29 15:43:30 -07:00
upgrade-zulip Improve shell quoting hygiene 2015-09-25 23:25:08 -04:00
upgrade-zulip-from-git refactor: Remove six.moves.configparser import. 2017-11-07 10:51:44 -08:00
zulip-puppet-apply refactor: Remove six.moves.configparser import. 2017-11-07 10:51:44 -08:00

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.