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.
- 01recondoes a swap (file, partition or zram) already exist? → do not add one
- 02reconfree space ≥ size + 20% and FS type (btrfs → mkswapfile, ext4/xfs → fallocate)
- 03reconis a swap entry already in fstab?
- 04recondoes /swapfile already exist? do not overwrite it
- 05reconopenvz/lxc: swap is impossible in a container → stop
- 06actCreate the ${size} fileverify
- 07actFormat and enableverify
- 08actMake persistent (fstab)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.
- 01verifyCreate the ${size} fileVerified by
stat -c '%a %s' /swapfile - 02verifyFormat and enableVerified by
swapon --show=NAME --noheadings | grep -cx /swapfile - 03verifyMake persistent (fstab)Verified by
grep -c '^/swapfile[[:space:]]' /etc/fstab
SEC.03
Guardrails
Non-negotiable instructions the run must respect, whatever it finds on the server.
Swap already present → report, do not add one. Free space < size + 20% → stop. Never touch a swap partition or an existing fstab line. A single fstab line.
SEC.04
Variables
What you choose before launching — the recipe fills in the rest.
| Name | Meaning |
|---|---|
| ${size} | Size |
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.
search by intent — type “firewall”, get ufw
- 01Read-only reconnaissance before any change
- 02Every command signed by your browser, approved by you
- 03Each step verified before the run moves on, every run kept in the history
SEC.06
Deploy on Servor button
Maintain Swap file 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
- 01restic backupsrestic + a scheduled, encrypted backup of a folder to a repository.
- 02MinIOS3-compatible MinIO object storage via Docker, local-only. Community project archived: frozen image.
- 03Garage (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.
- 04Samba shareSamba file server (SMB). Destructive: creates a share and a user.
- 05Borg backupsBorgBackup + a scheduled encrypted backup of a folder.
Verified recipe
Run this recipe on your server
Connect a server, launch the recipe, and approve each step as Servor executes and verifies it. Free plan, no card required.