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.
- 01recondistribution, version and package manager (apt or dnf)
- 02reconMySQL or MariaDB already present? (MariaDB installed → do not install MySQL)
- 03reconan active MySQL/MariaDB service?
- 04reconport 3306 already taken?
- 05reconexisting configuration, its location and bind-address
- 06recondoes /root/.my.cnf already exist? (do not overwrite it)
- 07actInstall MySQLverify
- 08actEnable and startverify
- 09actProtect root (only if root has no password)verify
- 10actHarden the installationverify
- 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.
- 01verifyInstall MySQLVerified by
mysqld --version - 02verifyEnable and startVerified by
systemctl is-active mysql mysqld 2>/dev/null | grep -c '^active' - 03verifyProtect root (only if root has no password)Verified by
mysql -NBe 'select 1' - 04verifyHarden the installationVerified by
mysql -NBe "select count(*) from mysql.user where user=''" - 05verifyListen on localhost onlyVerified by
ss -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.
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.
SEC.06
More database recipes
- 01PostgreSQLPostgreSQL (major version of your choice) from the official PGDG repository, initialized and verified.
- 02MariaDBMariaDB, secured, bound to localhost, started and verified.
- 03MongoDBMongoDB Community 9.0, local, with authentication enabled and verified.
- 04RabbitMQRabbitMQ broker (official repository) with management, local and a dedicated admin account.
- 05MemcachedMemcached in-memory cache, bound to localhost.
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.