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. 01reconrestic already installed?
2. 02recondoes the source folder exist?
3. 03actInstall resticverify
4. 04actInitialize the repositoryverify
5. 05actSchedule (${schedule})verify

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. 01verifyInstall resticVerified byrestic version
2. 02verifyInitialize the repositoryVerified bytrue
3. 03verifySchedule (${schedule})Verified bysystemctl list-timers 2>/dev/null | grep -c restic

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 storage & backup recipes

1. 01Swap fileCreates a persistent swap file of the chosen size. Destructive: modifies /etc/fstab.
2. 02MinIOS3-compatible object storage MinIO via Docker.
3. 03Samba shareSamba file server (SMB). Destructive: creates a share and a user.
4. 04Borg backupsBorgBackup + a scheduled encrypted backup of a folder.
5. 05rclonerclone to sync to the cloud (S3, B2, Drive...).