Game Server Hub (SteamCmd)
A hub for dedicated game servers, started and controlled from a Telegram bot — Valheim first, with other titles designed to slot in later without touching the bot.
The idea
I wanted a few dedicated game servers running at home, without leaving a terminal open or remembering Docker commands to start them — just a message to a Telegram bot. The first title is Valheim, with a world that’s been alive for years and needed preserving, not recreated from scratch.
How it’s built
A custom Python Telegram bot talks to Docker through a socket proxy that grants it
only start/stop/restart permissions on containers — not full access to the Docker
engine. Only a short whitelist of Telegram users can issue commands. A registry file
(games.yaml) maps game names to their containers, so adding a new title later means
adding one line, not rewriting the bot.
Preserving the existing world
The Valheim save dates back several years and had to stay intact, not be recreated. The
data therefore lives on a host bind mount rather than a disposable Docker volume, with
hourly automatic backups. An environment variable (DATA_ROOT) keeps the data path
configurable, with an eye on eventually moving the whole hub to a dedicated NAS.
Status
Completed and deployed: the Valheim server and bot are running, the world loads correctly, and commands respond. The hub is designed to take on more servers (Killing Floor 2, Insurgency) through the same Docker image family, but it’s a closed project in its current form — no further work is planned.
Stack
Docker · Python (Telegram bot) · WSL2 · Docker Socket Proxy