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. 01recondistribution, version and package manager (apt or dnf)
  2. 02reconMySQL or MariaDB already present? (MariaDB installed → do not install MySQL)
  3. 03reconan active MySQL/MariaDB service?
  4. 04reconport 3306 already taken?
  5. 05reconexisting configuration, its location and bind-address
  6. 06recondoes /root/.my.cnf already exist? (do not overwrite it)
  7. 07actInstall MySQLverify
  8. 08actEnable and startverify
  9. 09actProtect root (only if root has no password)verify
  10. 10actHarden the installationverify
  11. 11actListen on localhost onlyverify

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. 01Install MySQLVerified bymysqld --version
  2. 02Enable and startVerified bysystemctl is-active mysql mysqld 2>/dev/null | grep -c '^active'
  3. 03Protect root (only if root has no password)Verified bymysql -NBe 'select 1'
  4. 04Harden the installationVerified bymysql -NBe "select count(*) from mysql.user where user=''"
  5. 05Listen on localhost onlyVerified byss -tlnH "sport = :3306"

SEC.03

Guardrails

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

If MySQL or MariaDB is already installed, do not reinstall: check and report. Debian does not ship MySQL: suggest install-mariadb. Never put a password in clear text in a displayed command; it lives in /root/.my.cnf (600). Do not drop any database other than test, nor any account used by an application.

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.

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.05

Deploy on Servor button

Maintain MySQL 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-mysql)

SEC.06

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.