Well, I'm migrating my stuff to a mono-repo, all my projects have a docker-compose.yml,
concatenating these allows me to deploy everything in the repo, those that haven't changed won't change, but those that have will be updated to the latest $TAG
I find that easier to handle than having to create a pipeline fro each of my applications.
Docker-compose doesn't support swarms the same way, you'll be able to make different deployment specific changes. It just takes the docker-compose file and appends to the stack.
Sorry for the late response.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
You can use your docker-compose.yml with Stack deployment, by adding an image tag to your service you might make it easier for yourself.
Remember the compose also takes env variables, so adding $REGISTRY/$IMAGE_NAME:$TAG might assist you with your deploys :-)
NB: environment variables have to exist aswell, what is your ci tool?
I am currently not using a specific CI tool, as my repo should be a generic boilerplate to kick-start new projects.
What would be the benefits of docker stack deployments over docker-compose?
Well, I'm migrating my stuff to a mono-repo, all my projects have a docker-compose.yml,
concatenating these allows me to deploy everything in the repo, those that haven't changed won't change, but those that have will be updated to the latest $TAG
I find that easier to handle than having to create a pipeline fro each of my applications.
Docker-compose doesn't support swarms the same way, you'll be able to make different deployment specific changes. It just takes the docker-compose file and appends to the stack.
Sorry for the late response.