mirror of
https://github.com/zulip/zulip.git
synced 2025-10-30 19:43:47 +00:00
bf029d99f1
There is no reason to limit this to 640; mark it 644 for consistency with the other file.
30 lines
1.4 KiB
Bash
Executable File
30 lines
1.4 KiB
Bash
Executable File
#!/usr/bin/env bash
|
|
|
|
set -e
|
|
|
|
"$(dirname "$0")/zulip-puppet-apply" -f
|
|
# The step above should have generated the config files, now we need to move them into place:
|
|
chown root:root /etc/zulip/nginx_sharding.conf.tmp
|
|
chmod 644 /etc/zulip/nginx_sharding.conf.tmp
|
|
chown zulip:zulip /etc/zulip/sharding.json.tmp
|
|
chmod 644 /etc/zulip/sharding.json.tmp
|
|
mv /etc/zulip/nginx_sharding.conf.tmp /etc/zulip/nginx_sharding.conf
|
|
mv /etc/zulip/sharding.json.tmp /etc/zulip/sharding.json
|
|
|
|
# In the ordering of operations below, the crucial detail is that
|
|
# zulip-django and zulip-workers:* need to be restarted before
|
|
# reloading nginx. Django has an in-memory map of which realm belongs
|
|
# to which shard. Reloading nginx will cause users' tornado requests
|
|
# to be routed according to the new sharding scheme. If that happens
|
|
# before Django is restarted, updating its realm->shard map, users on
|
|
# realms, whose shard has changed, will have their tornado requests
|
|
# handled by the new tornado process, while Django will still use the
|
|
# old process for its internal communication with tornado when
|
|
# servicing the user's requests. That's a bad state that leads to
|
|
# clients getting into reload loops ending in crashing on 500 response
|
|
# while Django is restarting. For this reason it's important to
|
|
# reload nginx only after Django.
|
|
supervisorctl restart zulip-django
|
|
supervisorctl restart zulip-workers:*
|
|
service nginx reload
|