Skip to content

nginx: drop stale LazyResolve comment in nginx.conf.tmpl #373

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
acamarata merged 1 commit into from
Sep 4, 2026
Merged

nginx: drop stale LazyResolve comment in nginx.conf.tmpl #373

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
9 changes: 5 additions & 4 deletions internal/nginx/templates/nginx.conf.tmpl
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -33,10 +33,11 @@ http {
# Docker's embedded DNS (127.0.0.11) resolves container names on the
# user-defined bridge network. valid=10s keeps the cache short so a
# recreated container (new IP) is picked up on the next request instead
# of causing 502s until a manual `nginx -s reload`. Only takes effect
# for proxy_pass targets expressed via an nginx variable (see
# service.conf.tmpl LazyResolve) — static `upstream {}` blocks resolve
# once at load time regardless of this directive.
# of causing 502s until a manual `nginx -s reload`. Every proxy_pass in the
# generated site configs goes through an nginx variable
# (`set $up_x ...; proxy_pass $up_x`, see service.conf.tmpl), so this
# resolver governs all of them; static `upstream {}` blocks, which resolve
# once at load time, were removed in #364.
resolver 127.0.0.11 valid=10s ipv6=off;
resolver_timeout 5s;

Expand Down
Loading