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. 01recondisk space before cleanup
2. 02reconwhat is reclaimable (Docker: report only)
3. 03reconsize of the systemd journals
4. 04recondistro → apt or dnf; running kernel (never remove it)
5. 05reconpackages autoremove would remove: show them first
6. 06reconlargest folders (report, delete nothing)
7. 07actClear the package cacheverify
8. 08actVacuum the journals (> 7 days)verify
9. 09actRemove orphaned packagesdestructiveverify
10. 10actDelete archived logs older than 7 daysdestructiveverify
11. 11actFreed space reportverify

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. 01verifyClear the package cacheVerified bydu -sh /var/cache/apt/archives 2>/dev/null || du -sh /var/cache/dnf
2. 02verifyVacuum the journals (> 7 days)Verified byjournalctl --disk-usage
3. 03verifyRemove orphaned packagesVerified byapt-get -s autoremove 2>/dev/null | grep -c '^Remv' || dnf -q autoremove --assumeno
4. 04verifyDelete archived logs older than 7 daysVerified byfind /var/log -type f \( -name '*.gz' -o -name '*.[0-9]' -o -name '*.old' \) -mtime +7 | wc -l
5. 05verifyFreed space reportVerified bydf --output=avail -h / | tail -1

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 Disk cleanup 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 system recipes

1. 01TimezoneSets the server timezone.
2. 02CockpitCockpit web administration console, local-only (SSH tunnel) by default, on :9090.
3. 03Zsh + Oh My ZshZsh with Oh My Zsh for the current user.
4. 04Synchronized clock (chrony)NTP synchronization via chrony.
5. 05User + sudoCreates a user with SSH key and sudo access. Destructive: system account.