You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Feb 26, 2022. It is now read-only.
If DNS entries for non-local proxied things aren't available we almost certainly want NGINX to still start up. We should check that it has a sensible failure mode if the upstream still isn't around when a request comes in though.
The consensus seems to be that using a variable in the NGINX config is the way to achieve this:
If DNS entries for non-local proxied things aren't available we almost certainly want NGINX to still start up. We should check that it has a sensible failure mode if the upstream still isn't around when a request comes in though.
The consensus seems to be that using a variable in the NGINX config is the way to achieve this:
(both say the same thing)
https://www.nginx.com/blog/dns-service-discovery-nginx-plus/ appears to have more detailed information.
The text was updated successfully, but these errors were encountered: