ignacionelson f9e08412f2 Still log a failing health check in the production image ...

#1804 dropped every /up request from the nginx access log, so the
container's health checks stopped flooding `docker logs`. That also hid
the failing ones: when the container goes unhealthy, the 5xx from /up is
the line someone looks for, and Docker's health status alone does not say
why.

Key the map on the status as well as the path, so only a 2xx /up is
dropped. Verified against the 2.6.0 image: a 503 /up logs, a 200 /up does
not, and a 200 /upload still logs.

2026-10-01 15:24:08 -03:00

..

app

Say which step is missing instead of failing blankly (#1633)

2026-08-15 02:21:29 -03:00

clamav

Close the gaps an end-to-end and security pass found in virus scanning

2026-09-17 02:48:03 -03:00

production

Still log a failing health check in the production image

2026-10-01 15:24:08 -03:00

web

Close four small gaps before the release goes out

2026-08-17 20:28:16 -03:00