Mirror
/
zulip
mirror of https://github.com/zulip/zulip.git
1
0
Fork 0
Code Issues Projects Releases Wiki Activity
zulip/scripts/setup/configure-rabbitmq

19 lines
808 B
Plaintext
Raw Normal View History

Add support for running OpenBSD in development environment.
2016-01-12 13:08:43 +01:00
#!/usr/bin/env bash
[manual] Use rabbitmq queue to process UserActivity. Before this is deployed, we need to install rabbitmq and pika on the target server (see the puppet part of this commit for how). When this is deployed, we need to start the new user activity bot: ./manage.py process_user_activity in the screen session on the relevant server, or user_activity logs won't be processed (which will eventually result in all users getting notifications about how their mirrors are out of date). (imported from commit 44d605aca0290bef2c94fb99267e15e26b21673b)
2013-01-11 21:16:42 +01:00
#
Change Humbug => Zulip in text/comments. (imported from commit 2f9d73431ae40e1b9e9e11bc2f4f62f566ae758a)
2013-08-06 21:32:15 +02:00
# Delete the "guest" default user and replace it with a Zulip user
[manual] Use rabbitmq queue to process UserActivity. Before this is deployed, we need to install rabbitmq and pika on the target server (see the puppet part of this commit for how). When this is deployed, we need to start the new user activity bot: ./manage.py process_user_activity in the screen session on the relevant server, or user_activity logs won't be processed (which will eventually result in all users getting notifications about how their mirrors are out of date). (imported from commit 44d605aca0290bef2c94fb99267e15e26b21673b)
2013-01-11 21:16:42 +01:00
# with a real password
Add support for running OpenBSD in development environment.
2016-01-12 13:08:43 +01:00
set -e
set -x
[manual] Use rabbitmq queue to process UserActivity. Before this is deployed, we need to install rabbitmq and pika on the target server (see the puppet part of this commit for how). When this is deployed, we need to start the new user activity bot: ./manage.py process_user_activity in the screen session on the relevant server, or user_activity logs won't be processed (which will eventually result in all users getting notifications about how their mirrors are out of date). (imported from commit 44d605aca0290bef2c94fb99267e15e26b21673b)
2013-01-11 21:16:42 +01:00
configure-rabbitmq: Add support for RABBITMQ_NODE flag. This can potentially be used by things like a Docker configuration that runs RabbitMQ on another server.
2017-04-19 07:48:40 +02:00
if [ -n "$RABBITMQ_NODE" ]; then
RABBITMQ_FLAGS="-n $RABBITMQ_NODE"
fi
Move bin/get-django-setting to scripts/.
2016-05-08 04:02:32 +02:00
RABBITMQ_USERNAME=$("$(dirname "$0")/../get-django-setting" RABBITMQ_USERNAME)
RABBITMQ_PASSWORD=$("$(dirname "$0")/../get-django-setting" RABBITMQ_PASSWORD)
configure-rabbitmq: Add support for RABBITMQ_NODE flag. This can potentially be used by things like a Docker configuration that runs RabbitMQ on another server.
2017-04-19 07:48:40 +02:00
sudo rabbitmqctl $RABBITMQ_FLAGS delete_user "$RABBITMQ_USERNAME" || true
sudo rabbitmqctl $RABBITMQ_FLAGS delete_user zulip || true
sudo rabbitmqctl $RABBITMQ_FLAGS delete_user guest || true
sudo rabbitmqctl $RABBITMQ_FLAGS add_user "$RABBITMQ_USERNAME" "$RABBITMQ_PASSWORD"
sudo rabbitmqctl $RABBITMQ_FLAGS set_user_tags "$RABBITMQ_USERNAME" administrator
sudo rabbitmqctl $RABBITMQ_FLAGS set_permissions -p / "$RABBITMQ_USERNAME" '.*' '.*' '.*'