Closed marceloavf closed 4 years ago
Hey @marceloavf , sorry for the delay.
First, let me suggest you to separate the first docker-compose file, you should be able to have the global Traefik in one docker-compose, deployed only once in a Docker Swarm cluster.
And then, another docker-compose file for your stack, that you can keep updating and re-deploying.
Second suggestion, Traefik is currently having issues with Consul in certain specific situations (generating and saving HTTPS certificates after a period of time). And there are a couple of issues open about that. I have to update DockerSwarm.rocks with that.
But for the time being, it's probably good idea to use a single Traefik: https://dockerswarm.rocks/traefik-with-volume/
Assuming the original issue was solved, it will be automatically closed now. But feel free to add more comments or create new issues.
Hi @tiangolo, first of all thank you for this awesome boilerplate.
I'm having some problems by trying to merge this example with yours in dockerswarm.rocks, I'm using docker swarm in my DigitalOcean server and creating some replicas of my node api, but I keep receiving some error messages in traefik logs:
I'm trying to keep them in the same domain, but access in different ports. My application is being expose in port 7070, it's working normally in development mode, it's almost equal to yours, but not in production.
Do you have any tips?
docker-compose-prod.yml
docker-compose.yml