Join GitHub today
GitHub is home to over 50 million developers working together to host and review code, manage projects, and build software together.
Sign upFast server replacement support/documentation #1467
Comments
buchdag
transferred this issue from nginx-proxy/docker-letsencrypt-nginx-proxy-companion
|
Apologies for submitting this to the wrong repository, I realize now that it did not belong there. |
|
So this is exactly how it works already. |
|
Is that documented somewhere ? I don't want to rely on a behavior that just happens to work the way I need it at the moment. |
|
I've got a similar problem. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I could not find any documentation on this topic, so I assume any behavior I would witness in testing is accidental and prone to change unless specified somehow.
I would like to know the path to effective replacing of servers/containers. What I mean by that is that in a scenario where I have a container A with
www.somedomain.comrunning, and I would like to replace container A with container B to hostwww.somedomain.comfrom now, it is not clear to me if there is any supported path short of shutting down A, then starting up B. To minimize outage time, it would be much preferable if I could just give B the appropriate environment variables, start it up, and the companion container would say "hey, this guy has the same VIRTUAL_HOST/LETSENCRYPT_HOST as container A, that sounds like he wants to replace A, so lets route future incoming connections to B".Is there any way to get that to work in the way I described ? Or if that is already the case, can we rely on that behavior not changing ?