Help to get this working #113
Replies: 1 comment 1 reply
-
It's definitely possible, although it would require slight modifications. Overall, you'd need to create a configuration that would allow all your stacks to be run in parallel. As you can see, your stack route does not contain the APP_NAME variable. Which means, if all your stacks were routed to be woken up, they'd be routing rules overlap with Traefik. Then no routing would be done. I think you only have to set your routes rules with your APP_NAME in it. (I'd do something like After that you can set the Sablier on your main compose file. Define the middleware in the dynamic config for each compose file and use them within your routers. But because your containers would be scaled to 0, it means that you won't be able to use labels with docker classic. |
Beta Was this translation helpful? Give feedback.
-
Wow looks amazing and something i was looking for a long time.
But i dont think it would work, i have a dev-setup with a lot of sites.
Main docker-compose.yml with traefik and some tooling apps(mailhog enz.)
And a sites folder with folders into into it for every sites(lamp stacks) with each a separate docker-compose file
I use labels for config of taefik and routing to the nginx container.
Right now i manually do a docker compose down/up to enable a site(running 100+ sites is taking to much resources), so this solution would be amazing.
Is there a way to get this working for my settup?
My setup
main docker-compose file:
My dynamic file only has:
My docker-compose of my lemp stack
How i work now. The main compose is always on, and i do a docker compose up -d and docker compose down if i'm working on a site
Beta Was this translation helpful? Give feedback.
All reactions