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)
- 02reconMongoDB already installed? which version?
- 03reconservice active?
- 04reconport 27017 free?
- 05reconarchitecture, AVX (required on x86_64) and RAM
- 06reconexisting config (bindIp, auth) and data already present
- 07actAdd the MongoDB 9.0 repositoryverify
- 08actInstall MongoDBverify
- 09actEnable and startverify
- 10actCreate the admin accountverify
- 11actEnable 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.
- 01verifyAdd the MongoDB 9.0 repositoryVerified by
ls /etc/apt/sources.list.d/mongodb-org-9.0.list /etc/yum.repos.d/mongodb-org-9.0.repo 2>/dev/null | head -1 - 02verifyInstall MongoDBVerified by
mongod --version | head -1 - 03verifyEnable and startVerified by
mongosh --quiet --eval 'db.adminCommand({ ping: 1 }).ok' - 04verifyCreate the admin accountVerified by
mongosh --quiet --eval "db.getSiblingDB('admin').getUser('admin') ? 'ok' : 'missing'" - 05verifyEnable authenticationVerified by
mongosh --quiet -u admin -p "$(cat /root/mongodb-admin.password)" --authenticationDatabase admin --eval 'db.adminCommand({ ping: 1 }).ok'
SEC.03
Guardrails
Non-negotiable instructions the run must respect, whatever it finds on the server.
Do not reinitialize an existing dataset; if MongoDB is already installed, check and report. No AVX on x86_64 → stop, mongod will not start. Keep bindIp on 127.0.0.1; never expose 27017 without auth. Do not use the distribution’s mongodb package.
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 MongoDB 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.
- 02MySQLMySQL Server, secured, bound to localhost, started and verified.
- 03MariaDBMariaDB, secured, bound to localhost, started 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.