Hi, I'm Clio, your slightly grumpy but friendly assistant, designed to help you with all your DevOps-related tasks using CLI programs.
MongoDB is a popular, open-source NoSQL database system that uses a document-oriented data model. It operates with documents in a human-readable JSON-like format. It's known for its scalability and flexibility, allowing for complex queries, indexing, real-time aggregation, and server-side JavaScript execution.
The Acornfile used to create a MongoDB based Acorn Service is available in the GitHub repository at https://github.com/acorn-io/mongodb. This service triggers the creation of a MongoDB database running in a single container which can easily be used by an application during development.
This MongoDB instance:
The Acorn image of this service is hosted in GitHub container registry https://ghcr.io/acorn-io/mongodb:v#.#-#
Currently this Acorn has the following configuration options:
These values can be changed using the serviceArgs property as follow:
services: db: { image: "ghcr.io/acorn-io/mongodb:v#.#-#" serviceArgs: { dbUser: "bar" dbName: "foo" } }
The examples folder at https://github.com/acorn-io/mongodb/tree/main/examples contains a sample application using this Service. This app consists of a Python backend based on the FastAPI library, it displays a web page indicating the number of times the application was called, a counter is saved in the underlying MongoDB database and incremented with each request. The screenshot below shows the UI of the example application.
To use the Mongo Service, we first define a service property in the Acornfile of the application, this one references the image of the MongoDB Acorn.
services: db: { image: "ghcr.io/acorn-io/mongodb:v#.#-#" }
Next we define the application container. This one can connect to the MongoDB service via environment variables whose values are set based on the service's properties.
containers: { app: { build: { context: "." target: "dev" } consumes: ["db"] ports: publish: "8000/http" env: { DB_HOST: "@{service.db.address}" DB_PORT: "@{service.db.port.27017}" DB_NAME: "@{service.db.data.dbName}" DB_USER: "@{service.db.secrets.user.username}" DB_PASS: "@{service.db.secrets.user.password}" } } }
Note: This example uses the auto-generated user, which is limited to the default database. We could have used the admin user instead, this one does not have any limitation on the whole mongodb instance:
containers: { app: { build: { context: "." target: "dev" } consumes: ["db"] ports: publish: "8000/http" env: { DB_HOST: "@{service.db.address}" DB_PORT: "@{service.db.port.27017}" DB_USER: "@{service.db.secrets.admin.username}" <-- using the admin user DB_PASS: "@{service.db.secrets.admin.password}" <-- using the admin pass } } }
This container is built using the Dockerfile in the examples folder. Once built, the container consumes the MongoDB service using the address and credentials provided via the dedicated variables.
This example can be run with the following command (to be run from the examples folder)
acorn run -n app
After a few tens of seconds an http endpoint will be returned. Using this endpoint we can access the application and see the counter incremented on each reload of the page.
Instead of managing your own Acorn installation, you can deploy this application in the Acorn Sandbox, the free SaaS offering provided by Acorn. Access to the sandbox requires only a GitHub account, which is used for authentication.
An application running in the Sandbox will automatically shut down after 2 hours, but you can use the Acorn Pro plan to remove the time limit and gain additional functionalities.
Luc Juggery is a Contributor at Acorn Labs. You can follow him on Twitter, Youtube and Medium