- Warn at startup when quest files are missing (clients crash without them) and point users to the download link - Fix Host config description: it's the advertised IP, not a bind address — 0.0.0.0 was wrong advice - Load bundled schemas (shops, events, gacha) in Docker init so new users get working demo data out of the box - Renumber duplicate patch schema 28 → 32 to resolve numbering collision - Fix patch schema example filename to use hyphens matching actual files
Docker for Erupe
Quick Start
-
From the repository root, copy and edit the config:
cp config.example.json docker/config.jsonEdit
docker/config.json— setDatabase.Hostto"db"and match the password todocker-compose.yml(default:password). -
Place your quest/scenario files in
docker/bin/. -
Start everything:
cd docker docker compose up
The database is automatically initialized and patched on first start via init/setup.sh.
pgAdmin is available at http://localhost:5050 (default login: user@pgadmin.com / password).
Building Locally
By default the server service pulls the prebuilt image from GHCR. To build from source instead, edit docker-compose.yml: comment out the image line and uncomment the build section, then:
docker compose up --build
Stopping the Server
docker compose stop # Stop containers (preserves data)
docker compose down # Stop and remove containers (preserves data volumes)
To delete all persistent data, remove these directories after stopping:
docker/db-data/docker/savedata/
Updating
After pulling new changes:
-
Check for new patch schemas in
schemas/patch-schema/— apply them via pgAdmin orpsqlinto the running database container. -
Rebuild and restart:
docker compose down docker compose build docker compose up
Troubleshooting
Postgres won't populate on Windows: init/setup.sh must use LF line endings, not CRLF. Open it in your editor and convert.