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 (home, shell)? do not overwrite it
2. 02reconis the public key valid (fingerprint shown)? otherwise stop
3. 03reconadmin group: sudo (Debian/Ubuntu) or wheel (RHEL/Fedora)
4. 04reconAllowUsers/AllowGroups that would block the new account? key location
5. 05recondoes the account already have a password (P/PS)?
6. 06actCreate the userverify
7. 07actPrepare ~/.sshverify
8. 08actInstall the SSH keyverify
9. 09actGenerated sudo password (only if sudo = true and no password)verify
10. 10actAdd to the sudo group (only if sudo = true)destructiveverify

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 bygetent passwd ${username}
2. 02verifyPrepare ~/.sshVerified bystat -c '%a %U' /home/${username}/.ssh
3. 03verifyInstall the SSH keyVerified bygrep -cxF '${pubkey}' /home/${username}/.ssh/authorized_keys && stat -c '%a %U' /home/${username}/.ssh/authorized_keys
4. 04verifyGenerated sudo password (only if sudo = true and no password)Verified bypasswd -S ${username} && stat -c '%a' /root/servor-${username}.password
5. 05verifyAdd to the sudo group (only if sudo = true)Verified bysudo -l -U ${username}

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 User + sudo 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 system recipes

1. 01TimezoneSets the server timezone.
2. 02CockpitCockpit web administration console, local-only (SSH tunnel) by default, 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.