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. 01reconElixir and Erlang/OTP already present? versions? (present → skip)
2. 02recondistro, version, architecture and package manager (apt-get → Debian/Ubuntu, dnf → RHEL/Fedora/Rocky/Alma)
3. 03reconElixir version offered by the distro
4. 04actInstall Elixir/Erlangverify
5. 05actCheck Mixverify

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 Elixir/ErlangVerified byelixir --version | tail -1
2. 02verifyCheck MixVerified bymix --version | 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 Elixir + Erlang 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 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.