You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Please describe your suggestion, and the problem it'd solve.
Currently the docker image mounts thumbnail to content/thumb which is very convoluted and LRRG will try to create a empty directory "thumb/ under content if user creates a thumbnail volume that mounts to content/thumb. Mounting a volume inside another bind mount should be avoided. I suggest either in tools/build/docker/Dockerfile remove
VOLUME [ "/home/koyomi/lanraragi/content/thumb" ]
alltogether and let user decide where thumbnails should be,
or change it to
VOLUME [ "/home/koyomi/lanraragi/thumb" ]
Additional context
none
The text was updated successfully, but these errors were encountered:
hmm, the idea with that mount was to keep the previous behavior where thumbnails were always in the content folder by default, but maybe I should just give up on that and have it in a fully separated folder for good.
Please describe your suggestion, and the problem it'd solve.
Currently the docker image mounts thumbnail to content/thumb which is very convoluted and LRRG will try to create a empty directory "thumb/ under content if user creates a thumbnail volume that mounts to content/thumb. Mounting a volume inside another bind mount should be avoided. I suggest either in
tools/build/docker/Dockerfile
removealltogether and let user decide where thumbnails should be,
or change it to
Additional context
none
The text was updated successfully, but these errors were encountered: