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. 02reconClickHouse already installed?
3. 03reconservice active?
4. 04reconHTTP 8123 / native 9000 ports free?
5. 05reconRAM (4 GB recommended) and free disk
6. 06reconexisting config (default user password already set?)
7. 07actAdd the ClickHouse repositoryverify
8. 08actInstall ClickHouseverify
9. 09actSet the default user passwordverify
10. 10actEnable and startverify
11. 11actCheck authenticationverify

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. 01verifyAdd the ClickHouse repositoryVerified byls /etc/apt/sources.list.d/clickhouse.list /etc/yum.repos.d/clickhouse.repo 2>/dev/null | head -1
2. 02verifyInstall ClickHouseVerified byclickhouse-server --version
3. 03verifySet the default user passwordVerified bygrep -c password_sha256_hex /etc/clickhouse-server/users.d/servor-default-password.xml
4. 04verifyEnable and startVerified bycurl -sf http://127.0.0.1:8123/ping
5. 05verifyCheck authenticationVerified byss -tlnH "sport = :8123"

SEC.03

Guardrails

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

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.

SEC.05

Deploy on Servor button

Maintain ClickHouse 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

1. 01PostgreSQLPostgreSQL (major version of your choice) from the official PGDG repository, initialized and verified.
2. 02MySQLMySQL Server, secured, bound to localhost, started and verified.
3. 03MariaDBMariaDB, secured, bound to localhost, started and verified.
4. 04MongoDBMongoDB Community 9.0, local, with authentication enabled and verified.
5. 05RabbitMQRabbitMQ broker (official repository) with management, local and a dedicated admin account.