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. 02reconVarnish already present? which version?
3. 03reconservice active?
4. 04recondoes a default.vcl exist? which backend does it point to?
5. 05reconis port 6081 already taken (by which process)?
6. 06recondoes the backend respond on 127.0.0.1:${backend_port}? (000 = nothing listening)
7. 07actInstall Varnish (if missing)verify
8. 08actPoint the backend to port ${backend_port}verify
9. 09actEnable and startverify
10. 10actVarnish responds on 6081verify

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 Varnish (if missing)Verified byvarnishd -V 2>&1 | head -1
2. 02verifyPoint the backend to port ${backend_port}Verified byvarnishd -C -f /etc/varnish/default.vcl >/dev/null 2>&1 && echo ok
3. 03verifyEnable and startVerified bysystemctl is-active varnish
4. 04verifyVarnish responds on 6081Verified bycurl -sI http://127.0.0.1:6081/ | grep -ci '^via:.*varnish'

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 Varnish Cache 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. 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.