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 + version
2. 02recondoes the source folder exist? size
3. 03reconrestic config / timer already in place? do not overwrite them
4. 04reconlocal repository already initialized? → never init again
5. 05reconlocal repository: free space, and same disk as the source? (to report)
6. 06recondistro → apt, dnf (Fedora) or dnf + EPEL (RHEL/Rocky/Alma)
7. 07actInstall resticverify
8. 08actGenerate the repository passwordverify
9. 09actWrite /etc/restic/restic.envverify
10. 10actInitialize the repository (if new)verify
11. 11actCreate the restic-backup serviceverify
12. 12actSchedule (${schedule})verify
13. 13actEnable the timerverify
14. 14actFirst backupverify

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. 02verifyGenerate the repository passwordVerified bystat -c '%a %U' /etc/restic/password
3. 03verifyWrite /etc/restic/restic.envVerified bystat -c '%a' /etc/restic/restic.env && grep -c '^RESTIC_REPOSITORY=' /etc/restic/restic.env
4. 04verifyInitialize the repository (if new)Verified bybash -c 'set -a && . /etc/restic/restic.env && restic cat config' >/dev/null && echo ok
5. 05verifyCreate the restic-backup serviceVerified bysystemd-analyze verify /etc/systemd/system/restic-backup.service 2>&1 | grep -c restic-backup
6. 06verifySchedule (${schedule})Verified bycat /etc/systemd/system/restic-backup.timer
7. 07verifyEnable the timerVerified bysystemctl is-active restic-backup.timer
8. 08verifyFirst backupVerified bybash -c 'set -a && . /etc/restic/restic.env && restic snapshots --latest 1'

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 restic backups 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. 02MinIOS3-compatible MinIO object storage via Docker, local-only. Community project archived: frozen image.
3. 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.
4. 04Samba shareSamba file server (SMB). Destructive: creates a share and a user.
5. 05Borg backupsBorgBackup + a scheduled encrypted backup of a folder.