best practic to manage a docker-compose stack with Gitlab CI?
For example we have an app container, a database and a redis container. We only change the app and others won't change and wont need redeployment. How should I create my docker-compose for that purpose? My gitlab-runner should not restart redis and DB containers on every code push.
thanks
separation of concern. create independent docker-compose file.
so this way, if I specify the same network in both files, will they access each other? I mean the app, DB and redis?
there should be a way that docker compose can access already existed network
https://docs.docker.com/compose/networking/#use-a-pre-existing-network
Обсуждают сегодня