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.
- 01reconGo already present? version? does /usr/local/go exist? (same version → skip; distro golang package → leave it)
- 02recondistro, version, architecture and package manager (apt-get → Debian/Ubuntu, dnf → RHEL/Fedora/Rocky/Alma)
- 03reconat least ~500 MB free in /usr/local
- 04actDownload Go ${version}verify
- 05actInstall into /usr/local/goverify
- 06actMake go available system-wideverify
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.
- 01verifyDownload Go ${version}Verified by
tar -tzf /tmp/go.tar.gz go/VERSION - 02verifyInstall into /usr/local/goVerified by
/usr/local/go/bin/go version - 03verifyMake go available system-wideVerified by
/usr/local/bin/go version
SEC.03
Guardrails
Non-negotiable instructions the run must respect, whatever it finds on the server.
Never delete /usr/local/go: move it aside before extracting (extracting over an old version breaks Go). Do not remove the distro golang package. Official go.dev archive only.
SEC.04
Variables
What you choose before launching — the recipe fills in the rest.
| Name | Meaning |
|---|---|
| ${version} | Version |
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.
search by intent — type “firewall”, get ufw
- 01Read-only reconnaissance before any change
- 02Every command signed by your browser, approved by you
- 03Each step verified before the run moves on, every run kept in the history
SEC.06
Deploy on Servor button
Maintain Go 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
- 01Node.jsNode.js (LTS version of your choice) installed system-wide from the NodeSource repo.
- 02BunThe Bun JS runtime, installed system-wide in /usr/local/bin.
- 03PythonPython (version of your choice) via pyenv, for the user, without touching the system Python.
- 04RustThe stable Rust toolchain via rustup, for the user.
- 05DenoThe Deno runtime, installed system-wide in /usr/local/bin.
Verified recipe
Run this recipe on your server
Connect a server, launch the recipe, and approve each step as Servor executes and verifies it. Free plan, no card required.