HarpiG

GameKeepr is a self-hosted portal for the game servers on your Unraid box. The problem it solves: your friends' Valheim/Zomboid/whatever server needs a restart after a game update, and you're not home. With GameKeepr they sign in, see which servers are up and who's playing, and press Restart themselves — without touching Unraid, SSH, or anything else on your machine. I built it for my own friend group and it's been running our servers for a while now. Open source (MIT), runs as a single container. WHAT IT DOES Restarts that tell the truth: verified in two stages — container came back, then the game itself answered a query. Per-game startup times, a cooldown that stops restart-hammering, and an activity feed everyone can read. Install servers from the portal: from Community Applications templates (trusted publishers only, reviewed before deploy), or any of ~580 dedicated servers on Steam — GameKeepr composes the container itself on Valve's official steamcmd image. Schedules: nightly restart that first asks the game if anyone is online, never turns a deliberately stopped server back on. World backups (the saves, not the reinstallable gigabytes), with restore-only-while-stopped and a safety copy before every restore. Mods: repository installs (ficsit.app, Modrinth, Thunderstore) with hash verification and archive-safety checks, optional VirusTotal/ClamAV scanning, and Steam Workshop support for Zomboid/ARK. Live logs with a console input that types at the game (save-all, say, kick). Three roles (member / operator / owner) with per-server exceptions, Discord notifications, and a built-in wiki that documents everything. Screenshots and full documentation: https://kengoossens.github.io/Gamekeep/ THE HONEST PART — READ THIS BEFORE INSTALLING GameKeepr mounts the Docker socket, which is root-equivalent on your server. That is how it restarts and deploys containers; there is no way around it for this feature set (Unraid's own API can control containers but can't create them, run exec, or read files — I checked). What the code does about it: requests can never name a container directly (only whitelisted ids), it never deploys privileged containers, mod archives are parsed and judged before a byte is unpacked, and the optional docker-socket-proxy preset in the compose file is tested against every feature. Treat the owner password like your root password, and put Cloudflare Access or similar in front if you expose it to the internet. The wiki's "Security model" page spells all of this out. INSTALL Until it lands in CA (Unraid 7 removed the old "Template Repositories" field), fetch the template once from the Unraid terminal: curl -Lo /boot/config/plugins/dockerMan/templates-user/gamekeep.xml https://raw.githubusercontent.com/KenGoossens/Gamekeep/main/unraid/gamekeep.xml Then Docker → Add Container → pick GameKeepr from the Template dropdown (under User templates) — every field prefills. Set PUBLIC_URL and a SESSION_SECRET (openssl rand -hex 32), start it, and read the container log for the one-time SETUP TOKEN — the portal asks for it to create the owner account. Nobody can claim that account without reading your log. Two Unraid-specific notes: keep the data path on a pool (/mnt/cache/..., not /mnt/user — SQLite and FUSE don't get along), and set your appdata share's mover action to Array → Cache so the mover never migrates a live database off the pool. Source & issues: https://github.com/KenGoossens/Gamekeep Image: ghcr.io/kengoossens/gamekeep:latest (amd64) Feedback very welcome — especially which games you want in the registry (ports, save locations, player queries). Adding one is a single entry in one file.