adventurelog: route /media, /static, /admin, /accounts to the backend — photos rendered as broken content (R-483)
gates / gates (push) Successful in 1s

This commit is contained in:
2026-09-13 21:32:44 +02:00
parent 4cfac09bc4
commit 317225868c
2 changed files with 26 additions and 0 deletions
+11
View File
@@ -1,3 +1,14 @@
## adventurelog: photos render — the backend's own paths go to the backend (2026-09-13, R-483)
The operator measured it in a browser: on his k3s install a photo uploads and renders; on demo-hp it
uploads and renders as a broken "Uploaded content". The diff against `homelab-manifests`'s
`adventurelog-system/adventurelog.yaml`: its ingress sends `/media`, `/static`, `/admin` and
`/accounts` to the backend and only `/` to the frontend; the catalog template sent every path to the
frontend, which does not serve `/media`, so every photo URL was a 404. Now the backend service carries
its own traefik router for those four prefixes (priority 20; the frontend router is priority 10). The
frontend's `/api` and `/auth` proxy stays as it is — that is also the k3s shape. Nothing else differed
(`PUBLIC_URL`, `CSRF_TRUSTED_ORIGINS`, `ORIGIN`, `BODY_SIZE_LIMIT` all match). No version moved.
## catalog-since gate: an image move must bump catalog_since (2026-09-13, R-452)
`scripts/check-catalog-since.py`, fifth gate in `catalog_gates.py` (fast, git-history, `--range A..B`