zulip/tools/do-destroy-rebuild-database

#!/usr/bin/env bash
set -e
set -x

"$(dirname "$0")/../scripts/setup/terminate-psql-sessions" zulip zulip zulip_base

psql -h localhost postgres zulip <<EOF
DROP DATABASE IF EXISTS zulip;
CREATE DATABASE zulip TEMPLATE zulip_base;
EOF

sh "$(dirname "$0")/../scripts/setup/flush-memcached"

./manage.py migrate --noinput
./manage.py createcachetable third_party_api_results
./manage.py populate_db -n100 --threads=1
# Ensure that the local user's API key is synced from ~/.zuliprc

if [ -e ~/.zuliprc ]; then
    ./manage.py sync_api_key
fi
Add support for running OpenBSD in development environment. 2016-01-12 13:08:43 +01:00			`#!/usr/bin/env bash`
			`set -e`
			`set -x`
do-schema-change: Add comment about collation order consequences (imported from commit 19dc226e3af3ab6e6b17a35414617f2948d6de34) 2012-10-30 21:11:37 +01:00
Drop database users prior to DROP/CREATE database. This fixes an annoying issue where one tries to rebuild the database, and it fails due to there being existing connections. The one thing that is potentially scary about this implementation is that it means it's now a lot easier to accidentally drop your production database by running the wrong script; might be worth adding a "--force" flag controlling this behavior or something. Thanks to Nemanja Stanarevic and Neeraj Wahi for prototypes of this implementation! They did most of the work and testing for this. 2015-09-28 19:45:35 +02:00			`"$(dirname "$0")/../scripts/setup/terminate-psql-sessions" zulip zulip zulip_base`

Persist the tsearch_extras extension across rebuilding of the database We do this by creating a new zulip{_test}_base database that only has the zulip schema and the tsearch_extras extension. We then use that as a template when creating zulip{_test}. (imported from commit 8adb4b98410e4042a0187902e89c99561eac8c8f) 2014-01-30 23:40:37 +01:00			`psql -h localhost postgres zulip <<EOF`
			`DROP DATABASE IF EXISTS zulip;`
			`CREATE DATABASE zulip TEMPLATE zulip_base;`
			`EOF`
do-schema-change: Add comment about collation order consequences (imported from commit 19dc226e3af3ab6e6b17a35414617f2948d6de34) 2012-10-30 21:11:37 +01:00
Flush memcached whenever we drop the databases. This fixes some issues that we've had where commands will fail is confusing ways after the database is rebuilt because data from before the database was dropped is still in the memcached cache. 2015-09-28 19:57:40 +02:00			`sh "$(dirname "$0")/../scripts/setup/flush-memcached"`

Always start python via shebang lines. This is preparation for supporting using Python 3 in production. Signed-off-by: Anders Kaseorg <andersk@mit.edu> 2016-11-22 01:44:16 +01:00			`./manage.py migrate --noinput`
			`./manage.py createcachetable third_party_api_results`
			`./manage.py populate_db -n100 --threads=1`
Rename ~/.humbugrc to ~/.zuliprc. (imported from commit a0d53dd20097a56971874dc1d84c6f95267e84f2) 2013-08-07 17:36:46 +02:00			`# Ensure that the local user's API key is synced from ~/.zuliprc`
Disable sync_api_key if no zuliprc (imported from commit f9e7f924c00230137ca45c204158b709cd311ebb) 2015-06-10 20:28:02 +02:00
			`if [ -e ~/.zuliprc ]; then`
Always start python via shebang lines. This is preparation for supporting using Python 3 in production. Signed-off-by: Anders Kaseorg <andersk@mit.edu> 2016-11-22 01:44:16 +01:00			`./manage.py sync_api_key`
Disable sync_api_key if no zuliprc (imported from commit f9e7f924c00230137ca45c204158b709cd311ebb) 2015-06-10 20:28:02 +02:00			`fi`