AFAIK nginx-proxy does not enable true zero-downtime. Thus using this tool with nginx-proxy does not enable zero-downtime.
Example.
Deployment goes like this:
1) 2 app versions are deployed - blue (vCurrent) and green (vNext); both are up and ready to handle connections
2) We are about to shut down blue and replace it with green
3) Blue is handling long-running http request; receives shutdown signal; keeps handling long-running request, but does not accept new connections from now on
4) because it is still active (nginx-proxy wont remove it), blue will still receive connections from nginx-proxy, and all of them will fail because of reasons stated in (3)
Connections routed to green will succeed;
This is where zero-downtime fails.
5) Once long running request is handled, and blue removed from docker, only then nginx-proxy refreshes its configuration and routes all traffic to green.
If i am correct, this tool solves issue where non-working container are configured to receive traffic by nginx-proxy, but does not solve issue where partially shutdown old container still receices traffic and drops it.
I like "Kurzgesagt – In a Nutshell", its good information, easily understandable because its targeted to general population including kids. Perfect watch for tired brain after intense working session.
I have tried and still use different DEs, but for some time now Windows 10 DE is my favourite one. I think all others should just copy it, no need to reinvent the wheel.
Anything specifically you like about it? Tiling seems really limited, virtual desktops could still need more work, the search I have basically given up on (though "everything" is a kinda nice app for part of that), volume mixer widget is also very limited (e.g. see ear trumpet as an alternative), file manager still does not have tabs, network settings are convoluted (manual eduroam setup anyone?),...
Honestly, whenever I use windows it feels "okay" but I could not point at anything to say "oh, neat".
Example.
Deployment goes like this:
1) 2 app versions are deployed - blue (vCurrent) and green (vNext); both are up and ready to handle connections
2) We are about to shut down blue and replace it with green
3) Blue is handling long-running http request; receives shutdown signal; keeps handling long-running request, but does not accept new connections from now on
4) because it is still active (nginx-proxy wont remove it), blue will still receive connections from nginx-proxy, and all of them will fail because of reasons stated in (3) Connections routed to green will succeed; This is where zero-downtime fails.
5) Once long running request is handled, and blue removed from docker, only then nginx-proxy refreshes its configuration and routes all traffic to green.
If i am correct, this tool solves issue where non-working container are configured to receive traffic by nginx-proxy, but does not solve issue where partially shutdown old container still receices traffic and drops it.
I dont know about caddy-docker-proxy.