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. 01reconZsh already present + version
2. 02reconOh My Zsh already installed? do not overwrite it
3. 03reconexisting .zshrc: it will be kept (KEEP_ZSHRC)
4. 04recontarget user and current login shell
5. 05recongit + curl present? distro → apt or dnf
6. 06actInstall Zsh (+ git, curl)verify
7. 07actDownload the Oh My Zsh installerverify
8. 08actInstall Oh My Zshverify

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 Zsh (+ git, curl)Verified byzsh --version
2. 02verifyDownload the Oh My Zsh installerVerified byhead -1 /tmp/omz-install.sh
3. 03verifyInstall Oh My ZshVerified bytest -f "$HOME/.oh-my-zsh/oh-my-zsh.sh" && echo ok

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 Zsh + Oh My Zsh 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. 03Synchronized clock (chrony)NTP synchronization via chrony.
4. 04User + sudoCreates a user with SSH key and sudo access. Destructive: system account.
5. 05Log rotationConfigures logrotate for an application log folder.