PSA: filebrowser is no longer being actively developed
PSA: filebrowser is no longer being actively developed
github.com
š Need Maintainers Ā· filebrowser filebrowser Ā· Discussion #4906
15 comments
15 comments
PSA: filebrowser is no longer being actively developed
š Need Maintainers Ā· filebrowser filebrowser Ā· Discussion #4906
https://github.com/gtsteffaniak/filebrowser
File browser Quantum is the shiny feature rich fork!
I have also used filestash with some success
Trying to set that up to try out, but I can't get it to see/use my config.yaml.
/srv/filebrowser-new/data/config.yaml
volumes:
Says '/config/config.yaml' doesn't exist and will not start. Same thing if I mount the config file directly, instead of just its folder.
If I remove the env var, it changes to "could not open config file 'config.yaml', using default settings" and starts at least. From there I can 'ls -l' through docker exec and see that my config is mounted exactly where it's supposed to be '/config/config.yaml' and has 777 perms, but filebrowser insists it doesn't exist...
My config is just the example for now.
I don't understand what I could possibly be doing wrong.
/edit: three hours of messing around and I figured it out:
Must not have quotation marks. Removed them and now it's working.
Man that's finicky...
When the stable release is published, it's honestly a no brainer. Although Filestash is a good alternative too.
Ive had some good experience with filestash but recently they swapped to collabora which brought me a host of headaches.
The Dev is awesome though.
I was going to query why fork instead of just maintaining, but after reading theose comments I see the problem.
So, ok, I need to start shifting packages...
Reckon I can get this going somewhere where I don't have sudo?
I doubt it, why dont you have sudo?