register-referentie

eho/register-referentie

Fork 0

Author	SHA1	Message	Date
Niek Otten	8a537edd6c	fix(infra): engine-portable portal nginx resolver (closes #96 ) (#97 ) All checks were successful CI / lint (push) Successful in 1m28s Details CI / build (push) Successful in 1m18s Details CI / unit (push) Successful in 1m33s Details CI / frontend (push) Successful in 3m7s Details CI / mutation (push) Successful in 5m14s Details CI / verify-stack (push) Successful in 7m7s Details ## What & why Closes #96. The portal nginx configs hardcode `resolver 127.0.0.11` (Docker's embedded DNS) for their variable `proxy_pass` to the BFF, so on rootless podman (network-specific aardvark DNS) every proxied call 502'd — the portals loaded and login worked, but no in-app data flowed. Add a shared `/docker-entrypoint.d` hook (`apps/portal-nginx-resolver.sh`, wired into all three portal Dockerfiles) that rewrites the resolver from the container's own `/etc/resolv.conf` at startup: a no-op on Docker (nameserver is 127.0.0.11) and correct on podman (rewrites to e.g. 10.89.0.1). nginx.conf is unchanged (the hardcoded value is the substitution anchor). ## How verified Built the behandel image and ran it on the compose network under podman: the hook rewrote the config to `resolver 10.89.0.1`, and `GET /behandel/werkbak` proxied to the BFF returning 401 (auth), not 502. On Docker the nameserver is 127.0.0.11 so the substitution is a no-op and CI/e2e behaviour is unchanged. Reviewed-on: #97	2026-07-16 14:23:40 +00:00

Author

SHA1

Message

Date

Niek Otten

8a537edd6c

fix(infra): engine-portable portal nginx resolver (closes #96 ) (#97 )

CI / lint (push) Successful in 1m28s

Details

CI / build (push) Successful in 1m18s

Details

CI / unit (push) Successful in 1m33s

Details

CI / frontend (push) Successful in 3m7s

Details

CI / mutation (push) Successful in 5m14s

Details

CI / verify-stack (push) Successful in 7m7s

Details

## What & why

Closes #96. The portal nginx configs hardcode `resolver 127.0.0.11` (Docker's embedded DNS) for their variable `proxy_pass` to the BFF, so on rootless **podman** (network-specific aardvark DNS) every proxied call 502'd — the portals loaded and login worked, but no in-app data flowed.

Add a shared `/docker-entrypoint.d` hook (`apps/portal-nginx-resolver.sh`, wired into all three portal Dockerfiles) that rewrites the resolver from the container's own `/etc/resolv.conf` at startup: a **no-op on Docker** (nameserver *is* 127.0.0.11) and **correct on podman** (rewrites to e.g. 10.89.0.1). nginx.conf is unchanged (the hardcoded value is the substitution anchor).

## How verified

Built the behandel image and ran it on the compose network under podman: the hook rewrote the config to `resolver 10.89.0.1`, and `GET /behandel/werkbak` proxied to the BFF returning **401** (auth), not 502. On Docker the nameserver is 127.0.0.11 so the substitution is a no-op and CI/e2e behaviour is unchanged.

Reviewed-on: #97

2026-07-16 14:23:40 +00:00

Compare commits

1 Commits

fix/portal ... main

Diff Content Not Available

Compare commits

1 Commits fix/portal ... main

Diff Content Not Available

1 Commits

fix/portal ... main