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. 01reconNode already present? version and path (requested major already in /usr/bin → skip)
  2. 02recondistro, version, architecture and package manager (apt-get → Debian/Ubuntu, dnf → RHEL/Fedora/Rocky/Alma)
  3. 03reconNodeSource repo already configured? distro nodejs/npm package already installed (possible npm conflict)?
  4. 04recona version manager (nvm/fnm/volta) already in use — do not break it
  5. 05actAdd the NodeSource ${version}.x repoverify
  6. 06actInstall Node.js ${version}verify
  7. 07actCheck npmverify

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. 01Add the NodeSource ${version}.x repoVerified bygrep -rl "nodesource" /etc/apt/sources.list.d/ /etc/yum.repos.d/ 2>/dev/null | head -1
  2. 02Install Node.js ${version}Verified bynode -v
  3. 03Check npmVerified bynpm -v

SEC.03

Guardrails

Non-negotiable instructions the run must respect, whatever it finds on the server.

System-wide install in /usr/bin (persistent, no per-shell PATH). Do not reinstall if the requested major is already there. Never uninstall nvm/fnm/volta or an existing Node without consent. No curl | bash: download the script, then run it.

SEC.04

Variables

What you choose before launching — the recipe fills in the rest.

NameMeaning
${version}Major 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.

recipe — fail2ban_setup150+ in catalogue
security4 steps · low risk · idempotentrun
reconsshd present? ufw active? existing jails?✓
actinstall fail2ban · write default jails✓
actenable service · restart sshd (safe)✓
verifytest ban 60s · jails active · sshd alive✓

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 Node.js 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.

Deploy on ServorDark background
Deploy on ServorLight background
[![Deploy on Servor](https://servor.app/badges/deploy-on-servor.svg)](https://servor.app/deploy/install-nodejs)

SEC.07

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.