Skip to content

Latest commit

 

History

History
64 lines (47 loc) · 2.32 KB

README.md

File metadata and controls

64 lines (47 loc) · 2.32 KB
Raw

Eco

GitHub: https://github.com/IPS-Hosting/game-images/tree/main/eco

Basic usage

For advanced usage, refer to https://docs.docker.com

# Create the docker container
docker create -it --restart always \
  --name eco-server \
  -p 3000:3000/udp \
  -p 3001:3001/tcp \
  ipshosting/game-eco:v1
  
# Start the server
docker start eco-server

# Stop the server
docker stop eco-server

# Restart the server
docker restart eco-server

# View server logs
docker logs eco-server

# Attach to server console to write commands and see output in realtime (de-attach by pressing CTRL-P + CTRL-Q).
docker attach eco-server

# Remove the container
docker rm eco-server

Commands

By default, when starting the container, it will be installed and updated, and the eco Server is started afterwards. You can create a container with a different command to change this behaviour:

  • update Only install the latest version of the server. It won't be started and the container will exit after the eco server is installed and updated.
  • update_validate Same like update but will also validate the files. Recommended for the initial installation of the server.
  • start Only start the eco server without installing or updating.

Data persistence

Game server data is kept in /home/ips-hosting. By default a volume will be auto-created which will persist the game server data across server restarts. When you re-create the container, a new volume is created and you can't access the old data unless you manually mount the old volume. See https://docs.docker.com/storage/volumes/ for more information.

To persist the game server data on the host filesystem, use -v /absolute-path/on/host:/home/ips-hosting when creating the docker container.

Ports

  • 3000/udp (game)
  • 3001/tcp (web)

To use another port (e.g. to run multiple Eco servers on the same machine), change the docker port mapping when creating the container.

Env variables

Env variables can be configured with the -e "KEY=VAL" flag when creating the container. The flag can be used multiple times. To change the env variables, you need to re-create the container.

update and update_validate

The following env variables are available during update and update_validate.

BETA_BRANCH Used to download a different branch of the server.

BETA_PASSWORD The password for the beta branch.