Document the custom_zulip_files mechanism.

Also remove configure-rabbitmq, which is no longer used.
This commit is contained in:
Jason Michalski
2018-05-16 15:19:23 -07:00
committed by Tim Abbott
parent 0f07e4c97e
commit e1b4da877f
2 changed files with 10 additions and 16 deletions

View File

@@ -0,0 +1,10 @@
The custom_zulip_files mechanism allows you to test edits to Zulip
before making changes in the upstream repo. It works by copying the
contents of this directory on top of the main zulip/zulip checkout as
part of the Docker build process.
As an example, if you want to test a change to
`scripts/setup/generate-self-signed-cert`, you would grab a copy of
the script from zulip/zulip, place it at
`custom_zulip_files/scripts/setup/generate-self-signed-cert`, make
your local edits, and then run `docker-compose build`.

View File

@@ -1,16 +0,0 @@
#!/usr/bin/env bash
#
# Delete the "guest" default user and replace it with a Zulip user
# with a real password
set -e
set -x
RABBITMQ_HOST=$("$(dirname "$0")/../get-django-setting" RABBITMQ_HOST)
RABBITMQ_USERNAME=$("$(dirname "$0")/../get-django-setting" RABBITMQ_USERNAME)
RABBITMQ_PASSWORD=$("$(dirname "$0")/../get-django-setting" RABBITMQ_PASSWORD)
sudo rabbitmqctl -n "$RABBITMQ_HOST" delete_user "$RABBITMQ_USERNAME" || true
sudo rabbitmqctl -n "$RABBITMQ_HOST" delete_user zulip || true
sudo rabbitmqctl -n "$RABBITMQ_HOST" delete_user guest || true
sudo rabbitmqctl -n "$RABBITMQ_HOST" add_user "$RABBITMQ_USERNAME" "$RABBITMQ_PASSWORD"
sudo rabbitmqctl -n "$RABBITMQ_HOST" set_user_tags "$RABBITMQ_USERNAME" administrator
sudo rabbitmqctl -n "$RABBITMQ_HOST" set_permissions -p / "$RABBITMQ_USERNAME" '.*' '.*' '.*'