Portfolio images render low-res — likely Immich serving thumbnails instead of originals #25
Reference in New Issue
Block a user
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Images meant to showcase Elysse's work are displaying at low resolution on the site. Suspected cause: the Immich integration (
config/site.json→immich.baseUrl/publicAlbumPrefix, portfolio categoryimmichAlbumIds) is serving a thumbnail/preview asset rather than the full-resolution original — Immich's shared-album and asset endpoints have separate thumbnail vs. original routes, and it's easy to wire up the wrong one.To investigate:
/original) for both grid thumbnails and the expanded/lightbox viewdocs/BACKLOG-2026-07-16.md: "verify Immich proxy flow end-to-end on prod (couldn't test without albums)" — this may be the same root cause now that real albums/photos exist.Fix: ensure the lightbox/full-view image path requests full-resolution originals from Immich, reserving thumbnails for grid/card previews only.
Fixed and deployed to dev. Root cause: the portfolio grid requested Immich's default
/thumbnailendpoint with nosizeparam, which serves a 250x374 WebP (~10KB) — visibly blurry. Addedsize=preview, which returns a 1440x2157 JPEG (~330KB).Verified live on dev-lisilou.jerodrigged.com: deployed page's JS now builds URLs with
size=preview, and fetching an actual asset through that exact URL pattern confirms the 1440x2157 JPEG is served.Commit:
53677c9(pushed to main, deployed via Gitea Actions run #146).