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
I originally started writing this as a "doesn't work" ticket, but figured I had just misunderstood its purpose, so here is a feature request instead.
Currently, setting PUBLIC_FOLDER_PATH only changes where the internal webserver looks for static files.
What I'd like to see is it also being used for picking where the files get generated, instead of being hardcoded:
Reasoning behind wanting to put it elsewhere is so it can be accessed by another linux container via a bind mount.
Another reason would be to load the public folder with 2TB of waifus and not want that on my root drive.
EDIT: Found out that it also doesn't like inputting full paths either:
Aug 18 23:24:58 lewd node[2346]: Serving files from: /var/www/lewd2/packages/backend/dist/mnt/lewd/public/
The text was updated successfully, but these errors were encountered:
I originally started writing this as a "doesn't work" ticket, but figured I had just misunderstood its purpose, so here is a feature request instead.
Currently, setting PUBLIC_FOLDER_PATH only changes where the internal webserver looks for static files.
What I'd like to see is it also being used for picking where the files get generated, instead of being hardcoded:
lewd2/packages/frontend/build.js
Line 11 in a25241e
lewd2/packages/frontend/build.js
Line 18 in a25241e
Reasoning behind wanting to put it elsewhere is so it can be accessed by another linux container via a bind mount.
Another reason would be to load the public folder with 2TB of waifus and not want that on my root drive.
EDIT: Found out that it also doesn't like inputting full paths either:
The text was updated successfully, but these errors were encountered: