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 the user already exist? do not overwrite it
2. 02actCreate the userdestructiveverify
3. 03actInstall the SSH keyverify
4. 04actAdd to the sudo groupdestructiveverify

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 userVerified byid ${username} >/dev/null 2>&1 && echo ok
2. 02verifyInstall the SSH keyVerified bygrep -cF "${pubkey}" /home/${username}/.ssh/authorized_keys
3. 03verifyAdd to the sudo groupVerified byid -nG ${username} | grep -c sudo

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 system recipes

1. 01TimezoneSets the server timezone.
2. 02CockpitCockpit web administration console, on :9090.
3. 03Zsh + Oh My ZshZsh with Oh My Zsh for the current user.
4. 04Synchronized clock (chrony)NTP synchronization via chrony.
5. 05Log rotationConfigures logrotate for an application log folder.