Our great sponsors
-
InfluxDB
Power Real-Time Data Analytics at Scale. Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality.
git clone https://github.com/jagkt/local_dev_env.git cd local_dev_env
Now that we have our basic script to run the Node application, we'll create our base image. This time we will not be using the Dockerfile as we did earlier with the Python environment, but we will pull directly from the Docker Hub registry. Because we have multi-container services, it's best to orchestrate our services from a single file rather than building the services individually from a Dockerfile, which could be a daunting task if we need to build many services. Therefore, spinning up our Node containers with Docker Compose can be pretty handy in these situations. Note that Docker compose does not replace Dockerfile. Rather, the latter is part of a process to build Docker images, which are part of containers. Docker Compose allows us to operate the Node app alongside other services (assuming we have many services we need to spin up). In our case, it will be alongside our py service.
Related posts
- MongoDB on Your Local Machine Using Docker: A Step-by-Step Guide
- New computer? Install THIS first... 💻
- Live reload em Go com docker e compile daemon
- Docker compose, orchestrating and automating services
- Hosting a simple docker-compose app with Nginx and generate a SSL with certbot on digitalocean droplet