GameKeepr

Installing game servers

The Steam tab: every dedicated server Steam carries, recognised games first

Add server offers two routes. They differ in who you are trusting.

Unraid apps

Every game-server template in Community Applications, trusted publishers first. Publishers on the portal's trusted list (TRUSTED_PUBLISHERS in .env; ich777, binhex, linuxserver and friends by default) deploy without ceremony. Everyone else wears a community publisher badge and deploys only past an explicit warning you acknowledge — you are trusting that image's author with the server's data and your network, and the portal says so instead of deciding for you. Before anything is created, GameKeepr reviews the template and shows its findings: who published it, whether the image is what it claims, which paths it mounts. The hard refusals hold for every publisher, listed or not: privileged mode, host devices and host networking are refused outright — no game server needs root on the host. A template's ordinary host paths are not refused but ignored: every mount lands under the server's own directory, chosen by the portal; only dangerous paths (docker.sock, /etc and friends) refuse the deploy.

Steam

Any dedicated server Steam carries (~580 at the last count, recognised games sorted first), as a container GameKeepr composes itself on Valve's official steamcmd image. Here you trust exactly two parties — Valve's image and Steam's own depots — and the one thing in between is a start script GameKeepr writes, which lands in the server's own files where you can read it. (Windows-only servers add a third party: ich777's WineHQ base image, see below — the deploy form always names the image it will use.)

What both routes share

Validation runs (owner)

The Validation page: pick apps from either deploy path, run or schedule the proof

The Validation page lets the owner prove that what the portal offers still turns into working servers from nothing, on this very machine. Pick targets from both deploy paths — Unraid catalogue apps and Steam dedicated servers, through the same searches as the Add server tab — and each is deployed for real under a validation name, held to the same first-boot verification bar as any deploy, and then torn down completely — container, volume, downloads. Strictly one app at a time, so a run never competes with itself for disk, bandwidth or ports. A game the registry recognises proves itself by answering as the name it was given; any other app is verified as far as it honestly can be — its port accepting connections — and the outcome note says which bar was used.

The outcomes extend the verification's three with two honest extras: template refused (the app fails the same hard review a user's deploy would hit — privileged mode, host devices, host networking, or on the Steam path an app with neither a Linux nor a Windows build) and skipped (this attempt could not run right now — a leftover container wearing the validation name, a publisher outside the trusted list, whose image validation will not execute unattended even though a deploy may proceed acknowledged, or a Steam app that refuses anonymous downloads, which a validation run without an account cannot prove anything about).

Validation servers publish no host ports: nobody joins them, the verification talks over the internal Docker network, and a run therefore never collides with a live server of the same game — validating Terraria while Satisfactory holds port 7777 is a non-event. It also means a throwaway server never stands open on your LAN.

The deliberate price: every run downloads each game from scratch, because a warm cache would skip exactly the first-install experience being tested — hundreds of gigabytes for a full sweep. Run the full set once, then validate subsets. The result lands in a run history on the page and as one Discord summary (enable A validation run finished under Notifications). Validation servers never appear on the Servers page and never ping anyone mid-run.

A schedule makes it a standing instruction: save the current selection with a time and days (the night before a release is the classic), and the run fires on the portal's own clock. The same three rules as every schedule here: portal time, a missed minute stays missed, and a scheduled run never stacks on one already going.

Renaming and removing

Operators can rename a server from its card (the pencil, dimmed until hovered): only the display name changes — the container, the URLs and the artwork stay put. Servers listed by hand in config/servers.json are renamed in that file.

Two ways out, with very different weight:

A server listed by hand in config/servers.json deletes too, with one honest difference: the file is mounted read-only, so the portal records the entry as removed and stops listing it — schedules, access exceptions and caches go the same way — but the container (which the portal did not deploy) is left untouched. Delete the line from the file at your leisure; re-adding it later brings the server back.