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. 02reconPHP already present? which version?
3. 03recondoes a PHP-FPM already exist (which version, active)?
4. 04reconis the requested version in the distro repositories?
5. 05actAdd a PHP repository (only if the version is missing)verify
6. 06actInstall PHP-FPM ${version} + extensionsverify
7. 07actEnable the serviceverify
8. 08actFPM socket readyverify

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. 01verifyAdd a PHP repository (only if the version is missing)Verified byapt-cache policy php${version}-fpm 2>/dev/null | grep -c Candidate || dnf list php-fpm 2>/dev/null | grep -c php-fpm
2. 02verifyInstall PHP-FPM ${version} + extensionsVerified byphp -v | head -1
3. 03verifyEnable the serviceVerified bysystemctl is-active php${version}-fpm 2>/dev/null || systemctl is-active php-fpm
4. 04verifyFPM socket readyVerified bytest -S /run/php/php${version}-fpm.sock || test -S /run/php-fpm/www.sock && echo ok

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 PHP-FPM 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.