CodeYourFuture / CodeYourFuture/Module-Cloud
[TECH ED] Docker Compose
- Lenguaje dominante
- Sin datos de lenguaje
- Estrellas
- 0
- Forks
- 6
- Métricas de merge de PR
- Sin PR fusionados en 30 d
Descripción
### Link to the coursework
https://docs.docker.com/
### Why are we doing this?
Research Docker Compose, its syntax and a few examples. Think how it can help you orchestrate your 3 containers for local development, and then create a docker-compose file to use this tool to automatically build, start and network your containers. Find a way to specify dependencies, to ensure that the backend start initialising only when the database is up and running.
If you want, you can experiment with running all 3 components in EC2 via Docker compose, but keep it as an experiment. Think about some advantages and disadvantages of the 2 approaches (all in a docker-compose file inside a EC2 instance vs using multiple managed services such as S3 and RDS)
### How to get help
If you are doing this for the first time, **this will be hard**. You **must** reach out to volunteers to help you. Your ability to ask for help is actively assessed during this time. Ask good, curious questions with links, code samples, and no screenshots.
https://curriculum.codeyourfuture.io/guides/asking-questions/
You are **not** expected to be able to complete this module completely independently. You **are** expected to get help from volunteers.
### How to submit
In this advanced module you will demo your work. You may wish to make notes for case studies to add to your portfolio.
Guía de contribución
Línea de trabajo
Comienza con el enlace al trabajo práctico de Docker Compose e inspecciona los tres contenedores del proyecto y su configuración actual de compilación y arranque. Crea un archivo docker-compose que compile, inicie y conecte los contenedores en red, y que exprese la dependencia de la base de datos; valida el flujo de trabajo local y documenta el experimento de servicios gestionados frente a EC2 si se intentó.
Escrito por el modelo de indexación a partir del texto del issue.
Evaluación
- Stack tecnológico
- docker, docker-compose
- Área
- cloud, devops, infrastructure
- Tipo de issue
- Nueva funcionalidad
- Dificultad
- 4/5
- Tiempo estimado
- 3-5 días
- Estado de actividad
- Estancado
- Claridad
- Bastante claro
- Aptitud para principiantes
- 25/100