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?
2. 02recondo not run the runner as root
3. 03actDownload the runnerverify
4. 04actRegisterverify
5. 05actInstall the 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. 01verifyDownload the runnerVerified bytest -f /opt/actions-runner/config.sh && echo ok
2. 02verifyRegisterVerified bytest -f /opt/actions-runner/.runner && echo ok
3. 03verifyInstall the serviceVerified bycd /opt/actions-runner && ./svc.sh status 2>&1 | grep -c active

SEC.03

Variables

What you choose before launching — the recipe fills in the rest.

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

More ci/cd recipes

1. 01GitLab RunnerGitLab Runner registered with the Docker/shell executor.
2. 02Woodpecker CILightweight Woodpecker CI (server) via Docker.
3. 03Ansible (control node)Ansible installed as a control node.
4. 04systemd serviceDaemonize a command into a managed systemd service.
5. 05Scheduled task (cron)Add a scheduled task via a systemd timer.