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. 01reconHomebrew present? absolute path, prefix owner (brew refuses root: go through sudo -u <owner>), architecture
2. 02reconconsole user and admin group members (the owner must not be root)
3. 03reconCommand Line Tools present? (needed to build, not for bottles)
4. 04actSet the owner (only if an account is provided)verify
5. 05actDownload the official packageverify
6. 06actInstall Homebrewverify

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. 01verifySet the owner (only if an account is provided)Verified bystat -f "%Su %Lp" /var/tmp/.homebrew_pkg_user.plist
2. 02verifyDownload the official packageVerified bypkgutil --check-signature /var/tmp/Homebrew.pkg | head -3
3. 03verifyInstall HomebrewVerified byb=$(ls /opt/homebrew/bin/brew /usr/local/bin/brew 2>/dev/null | head -1); u=$(stat -L -f %Su "$b"); sudo -u "$u" -H "$b" --version | head -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 Homebrew 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 dev tools recipes

1. 01Node.jsNode.js (LTS version of your choice) installed system-wide from the NodeSource repo.
2. 02GoThe Go language (version of your choice) from go.dev, in /usr/local/go and on the PATH.
3. 03BunThe Bun JS runtime, installed system-wide in /usr/local/bin.
4. 04PythonPython (version of your choice) via pyenv, for the user, without touching the system Python.
5. 05RustThe stable Rust toolchain via rustup, for the user.