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. 01reconDocker Engine + compose plugin present?
2. 02reconexisting minio container/volume? → do not recreate, verify
3. 03reconports 9000/9001 free? (empty)
4. 04reconexisting deployment in /opt/minio? do not overwrite .env
5. 05reconRAM ≥ 1 GB free and disk space for the data
6. 06reconcan the frozen image still be pulled? otherwise stop
7. 07recondistro for the official Docker repository
8. 08actOfficial Docker repository (only if Docker is missing)verify
9. 09actDeclare the Docker apt source (Debian/Ubuntu, if Docker is missing)verify
10. 10actInstall Docker Engine (if missing)verify
11. 11actGenerate the admin credentialsverify
12. 12actWrite /opt/minio/compose.yamlverify
13. 13actStart MinIOverify
14. 14actHealth checkverify

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. 01verifyOfficial Docker repository (only if Docker is missing)Verified bytest -s /etc/apt/keyrings/docker.asc -o -f /etc/yum.repos.d/docker-ce.repo && echo ok
2. 02verifyDeclare the Docker apt source (Debian/Ubuntu, if Docker is missing)Verified bycat /etc/apt/sources.list.d/docker.list
3. 03verifyInstall Docker Engine (if missing)Verified bysystemctl is-active docker && docker compose version
4. 04verifyGenerate the admin credentialsVerified bystat -c '%a' /opt/minio/.env && grep -c '^MINIO_ROOT_' /opt/minio/.env
5. 05verifyWrite /opt/minio/compose.yamlVerified bydocker compose -f /opt/minio/compose.yaml config -q && echo ok
6. 06verifyStart MinIOVerified bydocker ps --filter name=^minio$ --format "{{.Status}}"
7. 07verifyHealth checkVerified bycurl -s -o /dev/null -w '%{http_code}' http://127.0.0.1:9000/minio/health/live

SEC.03

Guardrails

Non-negotiable instructions the run must respect, whatever it finds on the server.

SEC.04

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.05

Deploy on Servor button

Maintain MinIO 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.06

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