a3afa73b75
- Fixed potential startup and shutdown issues - Switched to a dedicated version of the server - Added a default configuration to avoid potential IP address binding issues - Added the ability to add unit tests in the future |
||
---|---|---|
.dockerignore | ||
.gitignore | ||
Dockerfile | ||
README.md | ||
docker_build.sh | ||
docker_build_force.sh | ||
docker_push.sh | ||
docker_run.sh | ||
goss.yaml | ||
goss_wait.yaml | ||
install.txt | ||
starbound_server.default.config | ||
start_starbound.sh |
README.md
Starbound server that runs inside a Docker container
NOTE: This image will install/update on startup. The path /steamcmd/starbound
can be mounted on the host for data persistence.
How to run the server
- Set the environment variables you wish to modify from below (note the Steam credentials)
- Optionally mount
/steamcmd/starbound
somewhere on the host or inside another container to keep your data safe - Enjoy!
Be sure to edit starbound_server.config
to further customize your installation.
The following environment variables are available:
STEAM_USERNAME (DEFAULT: "" - Required for installing/updating Starbound)
STEAM_PASSWORD (DEFAULT: "" - Required for installing/updating Starbound)
SKIP_STEAMCMD (DEFAULT: "" - Optional for skipping updating Starbound)
Updating the server
As long as you have both your STEAM_USERNAME
and STEAM_PASSWORD
set, simply restarting the container should trigger the update procedure.
Anything else
If you need help, have questions or bug submissions, feel free to contact me @Dids on Twitter.