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. 01reconCaddy already installed?
2. 02reconservice active?
3. 03reconports 80/443 free?
4. 04actAdd the Caddy repositoryverify
5. 05actInstall Caddyverify
6. 06actConfigure the domainverify
7. 07actReloadverify

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. 01verifyAdd the Caddy repositoryVerified byls /etc/apt/sources.list.d/caddy-stable.list 2>/dev/null && echo ok
2. 02verifyInstall CaddyVerified bycaddy version
3. 03verifyConfigure the domainVerified bycaddy validate --config /etc/caddy/Caddyfile
4. 04verifyReloadVerified bysystemctl is-active caddy

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 web server recipes

1. 01nginxnginx web server, started, enabled at boot and verified.
2. 02Apache httpdApache web server, started, enabled and verified.
3. 03HAProxyHAProxy load balancer, started and verified.
4. 04TraefikTraefik reverse proxy via Docker, with the dashboard and automatic TLS.
5. 05Nginx Proxy ManagerWeb-UI reverse proxy Nginx Proxy Manager via Docker.