Overview of building/deploying multi-container Applications using Docker Compose
When you have a multi-container Application that is defined using Compose, getting that setup for a streamlined Continuous Delivery and deep Insights is only few easy steps using the DevOps Templates. To learn more about the CloudMunch DevOps Templates please refer to the article here.
When to use this Template?
This Template is the ideal one for a multi-container Application with a Compose file defining the environment setup for that Application. As you know, Compose is great for development, testing, and staging environments, as well as CI workflows. Combine the power of Compose with the CloudMunch Platform to get a single place to manage everything DevOps for the Applications through powerful Application wide Insights.
Using this Template is basically a four-step process.
- Add GitHub account and repo of your Application
- Ensure the services that make up your Application are in a compose.yml file and provide the compose.yml path so they can be run together in an isolated environment.
- You can also provide your Application's environment with Dockerfile for each of the services in the Application so it can be reproduced anywhere or this can come from the compose.yml if using the context with Dockerfile specified in this yml file
- Lastly, provide the Hosts for the 3 stages of your Delivery Pipeline.
- GitHub account and a GitHub repo (can be public or private)
- Docker Hub account
- Docker host information
- GitHub Organization
- SonarQube server
What does this Template provide:
- Task to Build the Application based on the Dockerfile and Tasks to create multiple Roles based on the Compose.yml and Environment created for all services that makes up the Application
- Build automation directly from the Github Repo for the specified branch
- A default 3 stage Pipeline with Workflow Actions for a release cycle
- Tasks to provide Insights on the repo and Docker host usage
You can also read more details about this Template here.