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. 01reconnginx already installed? which version?
2. 02reconis the service already running?
3. 03reconis port 80 already taken (by what)?
4. 04recondoes an nginx config already exist? do not overwrite it
5. 05actInstall nginxverify
6. 06actEnable and startverify
7. 07actRespond 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. 01verifyInstall nginxVerified bynginx -v 2>&1
2. 02verifyEnable and startVerified bysystemctl is-active nginx
3. 03verifyRespond over HTTPVerified bycurl -sf -o /dev/null -w '%{http_code}' http://localhost/

SEC.03

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

More web server recipes

1. 01CaddyCaddy with automatic HTTPS for a domain.
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.