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. 01reconMariaDB already present?
2. 02reconservice active?
3. 03actInstall MariaDBverify
4. 04actEnableverify

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 MariaDBVerified bymariadb --version
2. 02verifyEnableVerified bysystemctl is-active mariadb

SEC.03

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

More database recipes

1. 01PostgreSQLPostgreSQL (major version of your choice), initialized, started and verified.
2. 02MySQLMySQL, secured (mysql_secure_installation), started and verified.
3. 03MongoDBMongoDB Community, started, enabled and verified.
4. 04RabbitMQRabbitMQ message broker with the management plugin.
5. 05MemcachedMemcached in-memory cache, bound to localhost.