discourse/bin/docker/reset_db

#!/bin/bash
SCRIPTPATH=$(cd "$(dirname "$0")" >/dev/null; pwd -P)
SOURCE_DIR=$(cd "$SCRIPTPATH" && cd ../.. && pwd -P)
DATA_DIR=$SOURCE_DIR/data/postgres

# Should this also run /etc/runit/1.d/ensure_database, or will that
# happen automatically? -- It will happen, but restarting the container is required
docker run -it -v $DATA_DIR:/shared/postgres_data discourse/discourse_dev:release /bin/bash -c "rm -fr /shared/postgres_data/*"
docker restart discourse_dev
echo "Creating admin user..."
"${SCRIPTPATH}/rake" admin:create
docker dev binaries 2015-11-01 20:33:08 -06:00			`#!/bin/bash`
FIX: reset_db (#5617) To get the database rebuilt requires a restart of the container. I also added a rake admin:create, since it's useful, and it's what `boot_dev --init `does. 2018-03-05 16:30:08 -06:00			`SCRIPTPATH=$(cd "$(dirname "$0")" >/dev/null; pwd -P)`
Improve the "develop inside Docker" experience This PR is intended to work in concert with the discourse_docker changes in https://github.com/discourse/discourse_docker/pull/292. I have used those changes to build a local "discourse_dev" image, and then _these_ changes to easily spin up and work on Discourse and plugin functionality. It's working well for me, but of course YMMV. Add `--init` and `--patch` options to bin/docker/boot_dev to make it easier to spin up a container running Discourse out of a development directory. Add `bin/docker/README.md` to explain how to go about using the docker command-line tools. Tweak the Docker command-line tools to use the `-u` option to specify user rather than changing to the user "inside" the container via `chpst` (This way, we don't have to explicitly specify the HOME environment variable, either.) Add `bin/docker/shell` command to make it easy to jump inside the running container. 2016-09-20 17:35:50 -05:00			`SOURCE_DIR=$(cd "$SCRIPTPATH" && cd ../.. && pwd -P)`
Move discourse dev data out of tmp Fix watch for restart so it works with puma 2017-05-18 10:36:12 -05:00			`DATA_DIR=$SOURCE_DIR/data/postgres`
docker dev binaries 2015-11-01 20:33:08 -06:00
Improve the "develop inside Docker" experience This PR is intended to work in concert with the discourse_docker changes in https://github.com/discourse/discourse_docker/pull/292. I have used those changes to build a local "discourse_dev" image, and then _these_ changes to easily spin up and work on Discourse and plugin functionality. It's working well for me, but of course YMMV. Add `--init` and `--patch` options to bin/docker/boot_dev to make it easier to spin up a container running Discourse out of a development directory. Add `bin/docker/README.md` to explain how to go about using the docker command-line tools. Tweak the Docker command-line tools to use the `-u` option to specify user rather than changing to the user "inside" the container via `chpst` (This way, we don't have to explicitly specify the HOME environment variable, either.) Add `bin/docker/shell` command to make it easy to jump inside the running container. 2016-09-20 17:35:50 -05:00			`# Should this also run /etc/runit/1.d/ensure_database, or will that`
FIX: reset_db (#5617) To get the database rebuilt requires a restart of the container. I also added a rake admin:create, since it's useful, and it's what `boot_dev --init `does. 2018-03-05 16:30:08 -06:00			`# happen automatically? -- It will happen, but restarting the container is required`
Fix docker image name (#8058) 2019-09-04 01:19:48 -05:00			`docker run -it -v $DATA_DIR:/shared/postgres_data discourse/discourse_dev:release /bin/bash -c "rm -fr /shared/postgres_data/*"`
FIX: reset_db (#5617) To get the database rebuilt requires a restart of the container. I also added a rake admin:create, since it's useful, and it's what `boot_dev --init `does. 2018-03-05 16:30:08 -06:00			`docker restart discourse_dev`
			`echo "Creating admin user..."`
			`"${SCRIPTPATH}/rake" admin:create`