Files
iot-dc3/dc3
pnoker ef2995c9b4 chore(nginx): adopt http2 directive and lift limit_req_zone to http scope
Upstream nginx 1.25 deprecated the "listen ... http2" parameter in
favour of a standalone "http2 on;" directive, and 1.27 emits a config
warning on the old form. Switch the default server to the new shape so
the dc3-web image stays clean on the pinned 1.27 base.

limit_req_zone is only valid in the http context — declaring it inside
the server block silently shadowed the rate-limit configuration on
reload. Move it up to nginx.conf:http so the api zone is actually
registered, while leaving limit_req_status in the server block where
the limit is consumed.

Dockerfile envsubst now whitelists ${APP_API_HOST} and ${APP_API_PORT}
so unrelated $-prefixed nginx variables in default.env aren't rewritten
to empty strings at container start.
2026-05-14 23:44:06 +08:00
..