liseur-sync/.github
Chmouel Boudjnah c2cb620964
fix(deploy): name the environment variables the server reads
Every deployment path set LISEUR_CONTENT_ROOT and LISEUR_LIBRARY_ROOTS.
The server reads LISEUR_CACHE_DIR and LISEUR_FOLDER_ROOTS. Unset,
cache_dir falls back to the relative "cache", which resolves inside the
image -- so on civuole the cover cache was sitting in
/home/nonroot/cache, in the container's writable layer, and `up -d`
threw it away on every update. Exactly what the comment beside the
variable said the variable was there to prevent.

Nothing failed, which is why it lasted: an unread variable is silent
and a discarded cache only costs the covers again. docs/deployment.md
had the right names all along; it was the Dockerfile, compose.yaml, the
systemd unit and CI that drifted.

The cache moves to /data/cache rather than reusing /data/content: that
directory still holds sha256/ and .incoming/ from the store this server
no longer has, and the cover cache should not move in beside them.
2026-08-18 22:29:57 +02:00
..
workflows fix(deploy): name the environment variables the server reads 2026-08-18 22:29:57 +02:00