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. 02reconApache already installed? (apache2 on Debian/Ubuntu, httpd on RHEL/Fedora)
3. 03reconservice active?
4. 04reconexisting vhosts? do not overwrite them
5. 05reconis port 80 already taken (by which process)? conflicting nginx/caddy?
6. 06reconis a firewall (ufw or firewalld) active?
7. 07actInstall Apache (if missing)verify
8. 08actValidate the configurationverify
9. 09actEnable and startverify
10. 10actOpen 80/443 (only if a firewall is active)verify
11. 11actRespond 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 Apache (if missing)Verified byapache2 -v 2>/dev/null || httpd -v
2. 02verifyValidate the configurationVerified byapachectl configtest 2>&1 | tail -1
3. 03verifyEnable and startVerified bysystemctl is-active apache2 2>/dev/null || systemctl is-active httpd
4. 04verifyOpen 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
5. 05verifyRespond over HTTPVerified bycurl -s -o /dev/null -w '%{http_code}' http://127.0.0.1/

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 Apache httpd 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. 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.