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. 01reconDocker present?
2. 02reconalready deployed?
3. 03actStart Giteaverify
4. 04actResponds over HTTPverify

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. 01verifyStart GiteaVerified bydocker ps --filter name=gitea --format "{{.Status}}" | grep -c Up
2. 02verifyResponds over HTTPVerified bycurl -sf -o /dev/null -w '%{http_code}' http://localhost:3000/

SEC.03

Variables

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

SEC.04

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.05

More self-hosted recipes

1. 01VaultwardenVaultwarden password manager (Bitwarden-compatible) via Docker.
2. 02Uptime KumaSelf-hosted uptime monitoring Uptime Kuma via Docker.
3. 03NextcloudNextcloud (self-hosted file cloud) via Docker.
4. 04JellyfinJellyfin media server via Docker, on :8096.
5. 05n8nn8n workflow automation via Docker.