Game servers
The Game space manages your game servers next to the repos that hold their content — live status, snapshots before risky changes, and module mappings that tie server paths to repos.
Servers and connectors
A server record names the game it runs and, optionally, the connector that controls the real machine. Servers with a connector are controllable: they report live status — running, stopped, starting, stopping, or error — straight from the host. Servers without a connector are tracked for content and deployments only.
Snapshots
Snapshots capture a server's state on demand — before a risky deployment, a mod update, or a world reset. Every snapshot records its status, size, start/completion times, and the reason it was taken, so the history reads as an audit trail.
Modules
Modules map paths inside a server's content to the GitForge repos that own them. That's what makes deployments git-driven: the content that lands on the server is the content in the repo at the ref you shipped.
Templates
Templates are pre-configured server definitions per game — a starting point for registering a new server without hand-writing its configuration.
API surface
# Game surface (session cookie or PAT auth)
GET /api/game/servers # paginated server list
GET /api/game/servers/:id # detail incl. live status
GET /api/game/servers/:id/snapshots # snapshot history
GET /api/game/servers/:id/modules # path -> repo mappings
GET /api/game/templates # per-game templates