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 device exist? partitions, FS, mount
2. 02reconsignature present (FS, LVM, RAID, partition table) = data → NEVER format
3. 03reconsystem disk: the device must not be part of it
4. 04recondevice member of an LVM, mdadm RAID or ZFS pool? → stop
5. 05reconexisting fstab entry for this device or mount point?
6. 06reconmount point already in use or not empty (its content would be hidden)?
7. 07reconFS tools present (e2fsprogs, xfsprogs, btrfs-progs)?
8. 08actInstall the FS tools (if missing)verify
9. 09actFormat ${device} (only if no signature)destructiveverify
10. 10actCreate the mount pointverify
11. 11actAdd to fstab (UUID, nofail)destructiveverify
12. 12actMountverify

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 the FS tools (if missing)Verified bycommand -v mkfs.${fs}
2. 02verifyFormat ${device} (only if no signature)Verified byblkid -s TYPE -o value ${device}
3. 03verifyCreate the mount pointVerified bytest -d ${mountpoint} && echo ok
4. 04verifyAdd to fstab (UUID, nofail)Verified bygrep -c "^UUID=$(blkid -s UUID -o value ${device}) " /etc/fstab
5. 05verifyMountVerified byfindmnt -n -o SOURCE,FSTYPE ${mountpoint}

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 Disk mount (fstab) 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 storage & backup recipes

1. 01Swap fileCreates a persistent swap file of the chosen size. Destructive: modifies /etc/fstab.
2. 02restic backupsrestic + a scheduled, encrypted backup of a folder to a repository.
3. 03MinIOS3-compatible MinIO object storage via Docker, local-only. Community project archived: frozen image.
4. 04Garage (S3 storage)Garage (Deuxfleurs) S3-compatible object storage via Docker, single-node and local-only, with a first bucket and its key. Maintained alternative to MinIO.
5. 05Samba shareSamba file server (SMB). Destructive: creates a share and a user.