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. 01recondistro and version: apt (Debian/Ubuntu) or dnf (RHEL/Fedora/Rocky/Alma)?
2. 02reconMosquitto already present? which version?
3. 03reconservice active?
4. 04reconexisting config: listeners, allow_anonymous, password_file, include_dir conf.d?
5. 05reconis port 1883 already taken (by which process)?
6. 06reconis a firewall (ufw or firewalld) active?
7. 07actInstall Mosquitto (if missing)verify
8. 08actCreate the ${mqtt_user} userverify
9. 09actListen with authenticationverify
10. 10actEnable and restartverify
11. 11actOpen 1883 (only if public exposure and an active firewall)verify
12. 12actPublish with 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. 01verifyInstall Mosquitto (if missing)Verified bycommand -v mosquitto mosquitto_passwd
2. 02verifyCreate the ${mqtt_user} userVerified bygrep -c "^${mqtt_user}:" /etc/mosquitto/passwd
3. 03verifyListen with authenticationVerified bygrep -rh "allow_anonymous false" /etc/mosquitto/ | head -1
4. 04verifyEnable and restartVerified bysystemctl is-active mosquitto
5. 05verifyOpen 1883 (only if public exposure and an active firewall)Verified byufw status 2>/dev/null | grep -c "^1883/tcp"; firewall-cmd --list-ports 2>/dev/null; true
6. 06verifyPublish with authenticationVerified bymosquitto_pub -h 127.0.0.1 -t servor/test -m ok -u ${mqtt_user} -P "$(cat /root/.servor/mosquitto-${mqtt_user}.pass)" && echo ok

SEC.03

Guardrails

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

SEC.04

Variables

What you choose before launching — the recipe fills in the rest.

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.

SEC.06

Deploy on Servor button

Maintain Mosquitto (MQTT) 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.07

More cache & queues recipes

1. 01RedisRedis, with an optional password, started and verified.
2. 02NATSNATS messaging server (JetStream optional).
3. 03Apache KafkaKafka in KRaft mode (no ZooKeeper) via Docker.