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.
- 01reconCockroachDB already present?
- 02reconservice active?
- 03reconSQL port 26257 and web console port free?
- 04reconarchitecture (amd64/arm64), RAM (2 GB minimum) and disk
- 05reconexisting store (do not wipe it)
- 06actInstall the CockroachDB binaryverify
- 07actCreate the user and the storeverify
- 08actCreate the systemd serviceverify
- 09actEnable and startverify
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 the CockroachDB binaryVerified by
cockroach version | head -1 - 02verifyCreate the user and the storeVerified by
stat -c %U /var/lib/cockroach - 03verifyCreate the systemd serviceVerified by
systemctl cat cockroach | grep -c start-single-node - 04verifyEnable and startVerified by
curl -s -o /dev/null -w '%{http_code}' --retry 10 --retry-connrefused 'http://127.0.0.1:${http_port}/health?ready=1'
SEC.03
Guardrails
Non-negotiable instructions the run must respect, whatever it finds on the server.
Insecure single-node = dev/small load only, never exposed: keep 127.0.0.1. Never wipe /var/lib/cockroach. No license is required for single-node; going multi-node requires one (point it out).
SEC.04
Variables
What you choose before launching — the recipe fills in the rest.
| Name | Meaning |
|---|---|
| ${version} | Version |
| ${http_port} | Web console port |
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.
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 CockroachDB 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.
Dark background
Light background[](https://servor.app/deploy/install-cockroachdb)SEC.07
More database recipes
- 01PostgreSQLPostgreSQL (major version of your choice) from the official PGDG repository, initialized and verified.
- 02MySQLMySQL Server, secured, bound to localhost, started and verified.
- 03MariaDBMariaDB, secured, bound to localhost, started and verified.
- 04MongoDBMongoDB Community 9.0, local, with authentication enabled and verified.
- 05RabbitMQRabbitMQ broker (official repository) with management, local and a dedicated admin account.
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.