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.
- 01recondistro, version and package manager (apt or dnf)
- 02reconDocker Engine + compose plugin present and running? (otherwise, docker step)
- 03reconserver already deployed (container, volume, /opt/terraria)? healthy → verify and skip; never reset a world or a save
- 04reconport 7777/tcp free?
- 05reconRAM ≥ 1 GB free (≥ 2 GB for a large world)
- 06reconactive firewall (ufw or firewalld)? a port is only opened if one is active
- 07actInstall Docker Engine + Compose (only if missing)verify
- 08actPrepare /opt/terraria/worldverify
- 09actStart the Terraria server (TShock)verify
- 10actOpen 7777/tcp (only if a firewall is active)verify
- 11actThe server is readyverify
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.
- 01verifyInstall Docker Engine + Compose (only if missing)Verified by
systemctl is-active docker && docker compose version - 02verifyPrepare /opt/terraria/worldVerified by
test -d /opt/terraria/world && echo ok - 03verifyStart the Terraria server (TShock)Verified by
docker inspect -f '{{.State.Status}}' terraria - 04verifyOpen 7777/tcp (only if a firewall is active)Verified by
ufw status 2>/dev/null | grep -cE '7777'; firewall-cmd --list-ports 2>/dev/null; true - 05verifyThe server is readyVerified by
timeout 270 bash -c 'until docker logs terraria 2>&1 | grep -q "Server started"; do sleep 10; done' && echo ready
SEC.03
Guardrails
Non-negotiable instructions the run must respect, whatever it finds on the server.
Never reset an existing world. On first start, TShock prints a /setup code in `docker logs terraria` to create the super-admin: tell the user where to find it, without copying it anywhere else. Only open 7777/tcp, only if a firewall is active.
SEC.04
Variables
What you choose before launching — the recipe fills in the rest.
| Name | Meaning |
|---|---|
| ${world_name} | World name |
| ${max_players} | Max players |
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.
search by intent — type “firewall”, get ufw
- 01Read-only reconnaissance before any change
- 02Every command signed by your browser, approved by you
- 03Each step verified before the run moves on, every run kept in the history
SEC.06
Deploy on Servor button
Maintain Terraria 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.
Dark background
Light background[](https://servor.app/deploy/install-terraria-server)SEC.07
More game servers recipes
- 01Minecraft Server (Java)Minecraft Java server (Paper, Vanilla, Fabric or Forge) under a dedicated user, as a systemd service, with the right Java.
- 02Valheim ServerDedicated Valheim server via Docker, under a dedicated user, world and backups in /opt/valheim.
- 03Factorio ServerDedicated Factorio server (stable release) via Docker, non-root, saves in /opt/factorio.
- 04Mumble ServerMumble (murmur) voice server from the distro packages, generated SuperUser password, started and verified.
- 05Minecraft Bedrock ServerDedicated Minecraft Bedrock server via Docker, under a dedicated user, world in /opt/bedrock.
Verified recipe
Run this recipe on your server
Connect a server, launch the recipe, and approve each step as Servor executes and verifies it. Free plan, no card required.