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. 01reconis a runner already installed and registered? (.runner present → do not re-register, check the service)
2. 02reconexisting runner services and their state
3. 03recondoes the dedicated github-runner user exist? (the runner never runs as root)
4. 04recondistro, version, architecture and package manager (apt-get → Debian/Ubuntu, dnf → RHEL/Fedora/Rocky/Alma)
5. 05reconDocker present? (if so, add github-runner to the docker group for container jobs)
6. 06actCreate the github-runner userverify
7. 07actDownload the runnerverify
8. 08actInstall the runner dependenciesverify
9. 09actRegister the runnerverify
10. 10actInstall the systemd serviceverify

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 github-runner userVerified byid github-runner
2. 02verifyDownload the runnerVerified bytest -x /opt/actions-runner/config.sh && echo ok
3. 03verifyInstall the runner dependenciesVerified byldd /opt/actions-runner/bin/Runner.Listener | grep -c "not found"
4. 04verifyRegister the runnerVerified bytest -f /opt/actions-runner/.runner && echo ok
5. 05verifyInstall the systemd serviceVerified bysystemctl is-active "$(cat /opt/actions-runner/.service)"

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 GitHub Actions Runner 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. 01GitLab RunnerGitLab Runner from the official repo, registered with the Docker or shell executor.
2. 02Woodpecker CILightweight Woodpecker CI (server + agent) via Docker Compose, behind an HTTPS reverse proxy.
3. 03Ansible (control node)Ansible installed as a control node from the distro packages.
4. 04systemd serviceDaemonize a command into a managed systemd service (auto-restart, at boot).
5. 05Scheduled task (cron)Add a scheduled task via a systemd timer (logged, catches up if missed).