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. 01reconNFS already installed? server active?
2. 02reconexisting exports (same path?): do not overwrite them
3. 03recondoes the folder exist? current permissions
4. 04recon2049 already in use?
5. 05recondistro (nfs-kernel-server or nfs-utils), firewall active
6. 06actInstall NFSverify
7. 07actCreate the exported folder (if missing)verify
8. 08actAdd the exportdestructiveverify
9. 09actEnable and publish the exportsverify
10. 10actAllow the ${allowed} network (only if a firewall is active)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 NFSVerified bycommand -v exportfs
2. 02verifyCreate the exported folder (if missing)Verified bytest -d ${export_path} && echo ok
3. 03verifyAdd the exportVerified bycat /etc/exports.d/servor.exports
4. 04verifyEnable and publish the exportsVerified byexportfs -v | grep -c "${export_path}"
5. 05verifyAllow the ${allowed} network (only if a firewall is active)Verified byufw status 2>/dev/null | grep 2049 || firewall-cmd --list-rich-rules

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 NFS server 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.