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. 01recondoes a service with the same name exist (where, active?) — if so, do not overwrite it without backup and consent
2. 02recondoes the user exist? (otherwise create it as a system account)
3. 03recondoes the command binary exist and is it executable? (ExecStart requires an absolute path)
4. 04actCreate the ${user} user (only if missing)verify
5. 05actWrite the unitverify
6. 06actEnable 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. 01verifyCreate the ${user} user (only if missing)Verified byid ${user}
2. 02verifyWrite the unitVerified bysystemd-analyze verify /etc/systemd/system/${name}.service && echo ok
3. 03verifyEnable and startVerified bysystemctl is-active ${name} && systemctl is-enabled ${name}

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 systemd service 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 ci/cd recipes

1. 01GitHub Actions RunnerSelf-hosted GitHub Actions runner under a dedicated user, registered as a systemd service.
2. 02GitLab RunnerGitLab Runner from the official repo, registered with the Docker or shell executor.
3. 03Woodpecker CILightweight Woodpecker CI (server + agent) via Docker Compose, behind an HTTPS reverse proxy.
4. 04Ansible (control node)Ansible installed as a control node from the distro packages.
5. 05Scheduled task (cron)Add a scheduled task via a systemd timer (logged, catches up if missed).