fix(serve): mount /healthz on the public origin #44

Merged

libretech merged 1 commits from fix/healthz-routing into main

2026-04-29 15:16:31 +02:00

Author	SHA1	Message	Date
libretech	2508d4fe28	fix(serve): mount /healthz on the public origin CI / ci (pull_request) Failing after 5m38s Details The /healthz route was registered inside httpapi.Server.Routes() but the root mux only attached that handler at /auth/ and /api/, so any request to /healthz fell through to the static file server and got 404'd. Caddy's reverse-proxy and the deploy workflow's curl-based health check both hit the public origin, so the in-container healthcheck reported 'unhealthy' and CI never marked the deploy as verified. Mount /healthz on the root mux explicitly. Add a serve_test.go that asserts the same routing topology so the regression cannot return silently.	2026-04-29 15:15:59 +02:00

Author

SHA1

Message

Date

libretech

2508d4fe28

fix(serve): mount /healthz on the public origin

CI / ci (pull_request) Failing after 5m38s

Details

The /healthz route was registered inside httpapi.Server.Routes() but
the root mux only attached that handler at /auth/ and /api/, so any
request to /healthz fell through to the static file server and got
404'd. Caddy's reverse-proxy and the deploy workflow's curl-based
health check both hit the public origin, so the in-container
healthcheck reported 'unhealthy' and CI never marked the deploy as
verified.

Mount /healthz on the root mux explicitly. Add a serve_test.go that
asserts the same routing topology so the regression cannot return
silently.

2026-04-29 15:15:59 +02:00