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. 02reconHAProxy already installed? which version?
3. 03reconservice active?
4. 04recondoes a config (frontends/backends) already exist? do not overwrite it
5. 05actInstall HAProxy (if missing)verify
6. 06actValidate the configverify
7. 07actEnable and startverify

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 HAProxy (if missing)Verified byhaproxy -v | head -1
2. 02verifyValidate the configVerified byhaproxy -c -f /etc/haproxy/haproxy.cfg >/dev/null 2>&1 && echo valid
3. 03verifyEnable and startVerified bysystemctl is-active haproxy

SEC.03

Guardrails

Non-negotiable instructions the run must respect, whatever it finds on the server.

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

Deploy on Servor button

Maintain HAProxy 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.06

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. 04TraefikTraefik reverse proxy via Docker, with the dashboard and automatic TLS.
5. 05Nginx Proxy ManagerWeb-UI reverse proxy Nginx Proxy Manager via Docker.