Docker container for running Schemaverse.
Docker Hub: https://hub.docker.com/r/frozenfoxx/schemaverse/
git clone git@github.com:frozenfoxx/docker-schemaverse.git
cd docker-schemaverse
docker build .
The following will run the latest Schemaverse server.
docker run -d --rm -p 5432:5432 --name=schemaverse_server frozenfoxx/schemaverse:latest
A good way to run for development and for continual monitoring is to attach to the terminal:
docker run -it --rm -p 5432:5432 --name=schemaverse_server frozenfoxx/schemaverse:latest
This image provides a persistent volume for /var/lib/postgresql if desired. If you wish to maintain the volume after the container is destroyed simply don't tell Docker to remove it with --rm. You can also override it:
docker run -d -p 5432:5432 -v /some/persistent/path:/var/lib/postgresql --name=schemaverse_server frozenfoxx/schemaverse:latest
Connecting to the running database is a lot like connecting to any other database. Assuming you're connecting to your schemaverse container on the same machine:
psql -U [some player] -h localhost schemaverse
Administering the database must be done from within the container. After starting the container you can perform the following to attach to its terminal and access the database:
docker ps
[note container id of the schemaverse container]
docker exec -it [container id] /bin/bash
su schemaverse -c "psql schemaverse"
Adding a player is very similar to administering the database. A script has been included to make this easier, add_player.sh. Invoke it as such:
docker ps
[note container id of the schemaverse container]
docker exec -it [container id] /src/schemaverse/scripts/add_player.sh [player name] [password]
The primary configuration is handled in conf/sqitch.conf. Update this file prior to building to alter deployment.