mirror of
https://github.com/zulip/zulip.git
synced 2026-06-21 21:32:29 +08:00
aff58ed9d9
We now just have two modes for setting up a dev/test
database. This makes it easy to see these things
side-by-side, when you're trying to understand how
the two different databases get built:
# dev:
USERNAME=zulip
DBNAME=zulip
STATUS_FILE_NAME=migration_status_dev
# test:
USERNAME=zulip_test
DBNAME=zulip_test
STATUS_FILE_NAME=migration_status_test
And then we make it more explicit the things that
are common between dev and test (which are
important things to understand when troubleshooting
provision-related glitches):
SEARCH_PATH=zulip,public
PASSWORD=$("$(dirname "$0")/../../scripts/get-django-setting" LOCAL_DATABASE_PASSWORD)
DBNAME_BASE=${DBNAME}_base
We lose some "generality" here, but passing in arbitrary
combinations of username/dbname/status_file to the script
would cause chaos for our digest checks, and all the different
template/base databases could cause confusion too.
|
||
|---|---|---|
| .. | ||
| dev-vagrant-docker | ||
| emoji | ||
| __init__.py | ||
| build_pygments_data | ||
| dev-motd | ||
| generate_integration_bots_avatars.py | ||
| generate_zulip_bots_static_files.py | ||
| generate-fixtures | ||
| generate-test-credentials | ||
| install-aws-server | ||
| install-sgrep | ||
| install-shellcheck | ||
| lang.json | ||
| optimize-svg | ||
| postgres-init-dev-db | ||
| postgres-init-test-db | ||
| setup_venvs.py | ||