Run MongoDB in Docker Container

For faster application development and delivery, Docker can be a good choice. MongoDB image has been available in the Docker registry. You can run MongoDB in Docker container then connect your application or service to it. To make the MongoDB service becomes available in the container's network and its data can be persisted, there are several steps for configuration.

1. Create named volumes for MongoDB data and a configuration file, then create a network for containers in your application system. For example, the volumes are my-mongo-data and my-mongo-config, and the network is named my-net.

docker volume create my-mongo-data
docker volume create my-mongo-config
docker network create my-net

2. As mentioned in MongoDB for Docker' site, database data is stored in the /data/db directory in the container. MongoDB for Docker also accepts environment variables for setting up initial username and password for root user which are named MONGO_INITDB_ROOT_USERNAME and MONGO_INITDB_ROOT_PASSWORD. To make the service can be simply accessible, in this case, the network alias is set to my-mongodb.

docker run -it -d --rm --network my-net -v my-mongodb-data:/data/db -v my-mongodb-config:/data/configdb -p 27017:27017 --network-alias my-mongodb --name my-mongodb -e MONGO_INITDB_ROOT_USERNAME=luki -e MONGO_INITDB_ROOT_PASSWORD=qwerty mongo

3. For setting up MongoDB connection string, we take sample parameters from the previous step, then it becomes as follows.

mongodb://luki:qwerty@my-mongodb:27017/?authMechanism=DEFAULT&authSource=admin

4. You can run your main application with additional environment variables. For example, we set MONGO_CONNECTION_STRING as MongoDB connection parameter and MONGO_DB as database name of the main application, in this sample its name is appDb.

docker run -it -d --rm --network my-net --network-alias app --name app -p 3000:5000 -e MONGO_CONNECTION_STRING=mongodb://luki:qwerty@mna-mongodb:27017/?authMechanism=DEFAULT"&"authSource=admin -e MONGO_DB=appDb your-app-image

Comments

Increase of Malicious Activities and Implementation of reCaptcha

In recent time, I've seen the increase of malicious activities such as login attempts or phishing emails to some accounts I manage. Let me list some of them and the actions taken. SSH Access Attempts This happened on a server that host a Gitlab server. Because of this case, I started to limit the incoming traffic to the server using internal and cloud firewall provided by the cloud provider. I limit the exposed ports, connected network interfaces, and allowed protocols. Phishing Attempts This typically happened through email and messaging platform such as Whatsapp and Facebook Page messaging. The malicious actors tried to share a suspicious link lured as invoice, support ticket, or something else. Malicious links shared Spammy Bot The actors leverage one of public endpoint on my website to send emails. Actually, the emails won't be forwarded anywhere except to my own email so this just full my inbox. This bot is quite active, but I'm still not sure what...

Configuring Swap Memory on Ubuntu Using Ansible

If we maintain a Linux machine with a low memory capacity while we are required to run an application with high memory consumption, enabling swap memory is an option. Ansible can be utilized as a helper tool to automate the creation of swap memory. A swap file can be allocated in the available storage of the machine. The swap file then can be assigned as a swap memory. Firstly, we should prepare the inventory file. The following snippet is an example, you must provide your own configuration. [server] 192.168.1.2 [server:vars] ansible_user=root ansible_ssh_private_key_file=~/.ssh/id_rsa Secondly, we need to prepare the task file that contains not only the tasks but also some variables and connection information. For instance, we set /swapfile as the name of our swap file. We also set the swap memory size to 2GB and the swappiness level to 60. - hosts: server become: true vars: swap_vars: size: 2G swappiness: 60 For simplicity, we only check the...

Deliver SaaS According Twelve-Factor App

If you haven't heard of the twelve-factor app , it gives us a recommendation or a methodology for developing SaaS or web apps structured into twelve items. The recommendation has some connections with microservice architecture and cloud-native environments which become more popular today. We can learn the details on its website . In this post, we will do a quick review of the twelve points. One Codebase Multiple Deployment We should maintain only one codebase for our application even though the application may be deployed into multiple environments like development, staging, and production. Having multiple codebases will lead to any kinds of complicated issues. Explicitly State Dependencies All the dependencies for running our application should be stated in the project itself. Many programming languages have a kind of file that maintains a list of the dependencies like package.json in Node.js. We should also be aware of the dependencies related to the pla...

Kenshin VS The Assassin

It is an assassin versus assassin.

Handling PDF Generation in Web Service

If we are building a website that requires a PDF generation feature, there are several options for implementing it based on the use cases or user requirements. First, we can generate the PDF on the client side using any available client library. It is suitable if the use case is to print out some data that is already available inside certain website components, and we want to maintain the styles of the components in the document. Second, we can do it fully in the back-end using any library available, such as PDF-lib, jsPDF, and so on. This approach is suitable if we want to keep the data processing or any related business functions in the back-end server. This second approach might have disadvantages, such as the difficulty of maintaining the design assets and styles which are already on our website. Third, it is using a hybrid approach, where certain processes are handled on the client side, and some are handled on the back-end. In this post, I want to discuss more about the...

Free Cloud Services from UpCloud

Although I typically deploy my development environment or experimental services on UpCloud , I do not always stay updated on its announcements. Recently, I discovered that UpCloud has introduced a new plan called the Essentials plan, which enables certain cloud services to be deployed at no cost. The complimentary services are generally associated with network components or serve as the foundation for other cloud services. This feature is particularly useful when retaining foundational services, such as a load balancer, is necessary, while tearing down all services and reconfiguring the DNS and other application settings each time we temporarily clean up infrastructure to reduce costs is undesirable. When reviewing the service specifications of the cloud services in the Essentials plan, they appear to be very similar to those in the Development plan. The difference in service levels is unclear, but it could be related to hardware or resource allocation. For instance, the loa...

LUKI NOTES

Search This Blog