Sign inSign up

bigboot/gigantic-server

By bigboot

•Updated almost 4 years ago

Docker Container for hosting a private Gigantic server

Image
0

449

bigboot/gigantic-server repository overview

⁠gigantic-server

Docker container for running a private Gigantic server.

The container contains the GCP⁠ for managing game instances which is exposed using traefik⁠ as reverse proxy.

Proton-GE⁠ is used as WINE runtime.

NOTE: A copy of Gigantic-Core_de build #298288 is required for running the server

NOTE: The ArcSDK.dll from "Gignatic-Core_de/Binaries/Win64/ArcSDK.dll" needs to be replaced with this patched ArcSDK.dll⁠

⁠Quickstart

The following command will run the GCP on Port 80/443

docker run                                               \
  --detach=false                                         \
  --name="gigantic-server"                               \
  --restart=always                                       \
  --env GCP_DOMAIN="eu.mistforge.net"                    \
  --env GCP_TITLE="Gigantic EU server"                   \
  --env GCP_MAX_INSTANCES="1"                            \
  --env GCP_API_KEY="12345"                              \
  --env ACME_EMAIL="[email protected]"                    \
  --env HTTP_USER="admin"                                \
  --env HTTP_PASSWORD="5up3r53cr37"                      \
  --env ACCESS_LOGS=no                                   \
  --volume /path/to/gigantic_core:/gigantic:ro           \
  --volume /path/to/data_folder:/data                    \
  --publish 80:8080                                      \
  --publish 443:8443                                     \
  --publish 8081:8081                                    \
  --publish 7777:7777/udp                                \
  bigboot/gigantic-server:latest
⁠Runtime flags explained
FlagExplanationDefault
--detach=falseset to true to run the container in the backgroundfalse
--name="gigantic-server"name of the container<random>
--restart=alwaysautomatically start the container when the Docker daemon startsno
--env GCP_DOMAIN="eu.mistforge.net"the domain which is shown in the GCP127.0.0.1
--env GCP_TITLE="Gigantic EU server"the title which is shown in the GCPGigantic Control Panel
--env GCP_MAX_INSTANCES="1"the maximum number of instances1
--env GCP_API_KEY="12345" the api key<disabled>
--env ACME_EMAIL="[email protected]" when set, the container will automatically try to request a certificate for the $GCP_DOMAIN from letsencrypt<disabled>
--env HTTP_USER="admin"if both $HTTP_USER and $HTTP_PASSWORD are set, enable basic auth for the GCP<disabled>
--env HTTP_PASSWORD="5up3r53cr37" if both $HTTP_USER and $HTTP_PASSWORD are set, enable basic auth for the GCP<disabled>
--env ACCESS_LOGS=no set to "yes" to enable access logno
--volume /path/to/gigantic_core:/gigantic:roreplace /path/to/gigantic_core with the path to the "Gigantic-Core_de" directory
--volume /path/to/data_folder:/datareplace /path/to/data_folder with the path to folder where the container can store it's data
--publish 80:8080publish the gcp http port
--publish 443:8443publish the gcp https port
--publish 8081:8081publish the traefik dashboard port
--publish 7777:7777/udppublish the game port. (When running multiple instances, add additional publishes accordingly)

Tag summary

Content type

Image

Digest

Size

498.4 MB

Last updated

about 5 years ago

docker pull bigboot/gigantic-server