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 and version: apt (Debian/Ubuntu) or dnf (RHEL/Fedora/Rocky/Alma)?
2. 02reconCaddy already installed? which version?
3. 03reconservice active?
4. 04recondoes a Caddyfile already exist and what does it serve? do not overwrite it without a backup
5. 05reconis port 80 already taken (by which process)? conflicting nginx/apache?
6. 06reconis port 443 already taken (by which process)?
7. 07recononly if a domain is provided: does it point to this server’s public IP? (required for the certificate)
8. 08reconis a firewall (ufw or firewalld) active?
9. 09actAdd the official Caddy repositoryverify
10. 10actInstall Caddyverify
11. 11actConfigure the domain (only if a domain is provided)verify
12. 12actEnable and reloadverify
13. 13actOpen 80/443 (only if a firewall is active)verify
14. 14actRespond over HTTP(S)verify

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 official Caddy repositoryVerified bytest -f /etc/apt/sources.list.d/caddy-stable.list && echo ok || dnf copr list 2>/dev/null | grep -c caddy
2. 02verifyInstall CaddyVerified bycaddy version
3. 03verifyConfigure the domain (only if a domain is provided)Verified bycaddy validate --config /etc/caddy/Caddyfile --adapter caddyfile 2>&1 | tail -1
4. 04verifyEnable and reloadVerified bysystemctl is-active caddy
5. 05verifyOpen 80/443 (only if a firewall is active)Verified byufw status 2>/dev/null | grep -E "^(80|443)/tcp"; firewall-cmd --list-services 2>/dev/null; true
6. 06verifyRespond over HTTP(S)Verified bycurl -s -o /dev/null -w '%{http_code}' https://${domain}/

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