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. 01reconCertbot already present?
2. 02recondo certificates already exist for this domain?
3. 03actInstall Certbotverify
4. 04actIssue the certificateverify
5. 05actTest renewalverify

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 CertbotVerified bycertbot --version
2. 02verifyIssue the certificateVerified bycertbot certificates 2>/dev/null | grep -c "${domain}"
3. 03verifyTest renewalVerified bysystemctl list-timers 2>/dev/null | grep -c certbot

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. 02CaddyCaddy with automatic HTTPS for a domain.
3. 03Apache httpdApache web server, started, enabled and verified.
4. 04HAProxyHAProxy load balancer, started and verified.
5. 05TraefikTraefik reverse proxy via Docker, with the dashboard and automatic TLS.