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. 01reconBorg already installed + version (1.2/1.4 expected; 2.x → different syntax)
2. 02recondoes the source folder exist? size
3. 03reconBorg 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 Borgverify
8. 08actGenerate the passphraseverify
9. 09actWrite /etc/borg/borg.envverify
10. 10actInitialize the repository (if new)verify
11. 11actExport the repository keyverify
12. 12actCreate the borg-backup serviceverify
13. 13actSchedule (${schedule})verify
14. 14actEnable the timerverify
15. 15actFirst 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 BorgVerified byborg --version
2. 02verifyGenerate the passphraseVerified bystat -c '%a %U' /etc/borg/passphrase
3. 03verifyWrite /etc/borg/borg.envVerified bystat -c '%a' /etc/borg/borg.env && grep -c '^BORG_REPO=' /etc/borg/borg.env
4. 04verifyInitialize the repository (if new)Verified bybash -c 'set -a && . /etc/borg/borg.env && borg info' >/dev/null && echo ok
5. 05verifyExport the repository keyVerified bystat -c '%a' /etc/borg/repo-key.txt
6. 06verifyCreate the borg-backup serviceVerified bysystemd-analyze verify /etc/systemd/system/borg-backup.service 2>&1 | grep -c borg-backup
7. 07verifySchedule (${schedule})Verified bycat /etc/systemd/system/borg-backup.timer
8. 08verifyEnable the timerVerified bysystemctl is-active borg-backup.timer
9. 09verifyFirst backupVerified bybash -c 'set -a && . /etc/borg/borg.env && borg list --last 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 Borg 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. 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.