SEC.01

The playbook

The run starts read-only: the recon probes decide what happens next. The steps that follow are adapted to the distribution and state found — a real machine is rarely clean.

1. 01recondistro, version and package manager (apt or dnf)
2. 02reconDocker Engine + compose plugin present and running? (otherwise, docker step)
3. 03reconserver already deployed (container, volume, /opt/cs2)? healthy → verify and skip; never reset a world or a save
4. 04reconports 27015 (tcp + udp) and 27020/udp free?
5. 05recon≥ 60 GB of free disk (required) and RAM ≥ 4 GB
6. 06reconactive firewall (ufw or firewalld)? a port is only opened if one is active
7. 07actInstall Docker Engine + Compose (only if missing)verify
8. 08actPrepare /opt/cs2/data (image UID 1000)verify
9. 09actStore the GSLT token and generate the RCON password (/opt/cs2/cs2.env)verify
10. 10actStart the CS2 serververify
11. 11actOpen 27015 (tcp + udp) + 27020/udp (only if a firewall is active)verify
12. 12actThe server runs without a restart loopverify

SEC.02

What it verifies

Each step ships its own check. The run only moves on when the check passes, so what the recipe reports as done is what is actually on the server.

1. 01verifyInstall Docker Engine + Compose (only if missing)Verified bysystemctl is-active docker && docker compose version
2. 02verifyPrepare /opt/cs2/data (image UID 1000)Verified bystat -c '%u:%g' /opt/cs2/data
3. 03verifyStore the GSLT token and generate the RCON password (/opt/cs2/cs2.env)Verified bystat -c '%a' /opt/cs2/cs2.env && grep -cE '^(SRCDS_TOKEN|CS2_RCONPW)=.' /opt/cs2/cs2.env
4. 04verifyStart the CS2 serverVerified bydocker inspect -f '{{.State.Status}}' cs2
5. 05verifyOpen 27015 (tcp + udp) + 27020/udp (only if a firewall is active)Verified byufw status 2>/dev/null | grep -cE '27015|27015|27020'; firewall-cmd --list-ports 2>/dev/null; true
6. 06verifyThe server runs without a restart loopVerified bysleep 270; docker inspect -f '{{.State.Status}} {{.RestartCount}}' cs2

SEC.03

Guardrails

Non-negotiable instructions the run must respect, whatever it finds on the server.

SEC.04

Variables

What you choose before launching — the recipe fills in the rest.

SEC.05

How a recipe runs in Servor

Servor is zero-knowledge: the platform cannot execute anything on its own. When you launch this recipe, a run reads the reconnaissance, plans the steps and asks for your approval. Each approved command is signed by your browser — with a key the server never sees — then relayed verbatim to the agent, which verifies the signature locally before executing.

SEC.06

Deploy on Servor button

Maintain CS2 Server or a project that needs it? Put this button in your README or on your site: one click and your users install it on their own server.

SEC.07

More game servers recipes

1. 01Minecraft Server (Java)Minecraft Java server (Paper, Vanilla, Fabric or Forge) under a dedicated user, as a systemd service, with the right Java.
2. 02Valheim ServerDedicated Valheim server via Docker, under a dedicated user, world and backups in /opt/valheim.
3. 03Factorio ServerDedicated Factorio server (stable release) via Docker, non-root, saves in /opt/factorio.
4. 04Mumble ServerMumble (murmur) voice server from the distro packages, generated SuperUser password, started and verified.
5. 05Minecraft Bedrock ServerDedicated Minecraft Bedrock server via Docker, under a dedicated user, world in /opt/bedrock.