Use docker-compose labels for frontend and backend names

[tcoupin]

Actually with a project "foo" and service "bar", traefik add a frontend and a backend for each container (foo-bar-1, foo-bar-2...)

Now, frontend and backend are named foo-bar and all the instances of a service are grouped in a single backend.

[emilevauge]

Hey @tcoupin, I think this is a great idea :)
What about Host:{service}.{project_name}.{domain} instead of Host:{project_name}-{service}.{domain} ?
/cc @vdemeester

[tcoupin]

Better Le 7 mars 2017 15:56, "Emile Vauge" <notifications@github.com> a écrit : Hey @tcoupin <https://github.com/tcoupin>, I think this is a great idea :) What wbout Host:{service}.{project_name}.{domain} instead of Host:{project_name}-{service}.{domain} ? /cc @vdemeester <https://github.com/vdemeester> — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#1235 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AHHKalo1HoAL9eCe4mfo-zuAWv-IbIKlks5rjXASgaJpZM4MTEuy> .

[tcoupin]

Just commit "Use service.project.domain instead of project-service.domain"

[vdemeester]

I am not a huge fan of that (because it's only for docker-compose user, it won't work with docker stack deploy and if something like docker-compose uses a different namespace for labels it won't work and we might have to add more and more in the future) but I can see how it can make sense. So it's a weak LGTM 🐸 from me, but a LGTM still 👼

[emilevauge]

LGTM
Thanks @tcoupin :)

[sarahconor]

Just upgraded to version 1.3.0 and this feature is causing me some issues. How can I default back the old behaviour (without changing dockerFiles) ? Host:{containerName}.{domain}

Thanks.

[emilevauge]

@sarahconor please, open an issue with a detailed description.