dsea/dst-server repository overview

Configure everything through environment vars. Sane defaults provided, and no need for volume mounts (though you can if you want to save state).

Quick list of environment vars available and what they do:

⁠CLUSTER_TOKEN

Your cluster token, get this from the game client, if you don't know how, google this: cluster_token dst Example: CLUSTER_TOKEN=aabbccddeeffgghhi1122334455

⁠ADMINS

Comma separated list of klei account IDs that should all be Admins on the server.
Example: ADMINS=ku_ab123cd,ku_5aabbcc

⁠ALL cluster.ini settings

Use the format SECTION_key=value. SECTIONs are GAMEPLAY, NETWORK, MISC, and SHARD. An example key in the GAMEPLAY section would be game_mode. So to set game_mode to survival in the [GAMEPLAY] section you would set this environment var: Example: GAMEPLAY_game_mode=survival All cluster.ini settings can be configured that way.

⁠Modules

ENABLE_MODS is a comma separated list of modules you want to install Example: ENABLE_MODS=cool-mod1,superman-mod,another-module ENABLE_COLLECTIONS is the same, but you can pass a comma separated list of module collections instead Example: ENABLE_COLLECTIONS=all-the-things,tons-of-cool-stuff

⁠Module configuration

CONFIG_ can be used to configure the module associated with MOD-NUMBER. So if your super-duper module has a steam workshop ID of 12345678, then you can configure it with CONFIG_12345678='exampleSetting = 1, anotherExample = 2, exampleString = "superduper", ["yet_another_example"] = "awesome"' Note that enabled="true" is added automatically when you enable a module OR configure a module so you don't need to add it unless you added a module through a COLLECTION and didn't configure it. If you add a module through a collection, you at least need to add a CONFIG_ for each module in the collection to enable each one. (long story short, it's easier to use ENABLE_MODS than ENABLE_COLLECTIONS)