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 daemon with the same label already exist?
2. 02reconalready loaded?
3. 03actWrite the LaunchDaemondestructiveverify
4. 04actLoad the servicedestructiveverify

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. 01verifyWrite the LaunchDaemonVerified byplutil -lint /Library/LaunchDaemons/${label}.plist
2. 02verifyLoad the serviceVerified bylaunchctl list | grep -c "${label}"

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. 01GitHub Actions RunnerSelf-hosted GitHub Actions runner, registered as a service.
2. 02GitLab RunnerGitLab Runner registered with the Docker/shell executor.
3. 03Woodpecker CILightweight Woodpecker CI (server) via Docker.
4. 04Ansible (control node)Ansible installed as a control node.
5. 05systemd serviceDaemonize a command into a managed systemd service.