When the stable release is published, it’s honestly a no brainer. Although Filestash is a good alternative too.
Comment on PSA: filebrowser is no longer being actively developed
kuvwert@lemmy.dbzer0.com 4 weeks ago
github.com/gtsteffaniak/filebrowser
File browser Quantum is the shiny feature rich fork
warmaster@lemmy.world 4 weeks ago
kuvwert@lemmy.dbzer0.com 4 weeks ago
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.
Cyber@feddit.uk 4 weeks ago
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…
beeng@discuss.tchncs.de 4 weeks ago
Reckon I can get this going somewhere where I don’t have sudo?
kuvwert@lemmy.dbzer0.com 4 weeks ago
I doubt it, why dont you have sudo?
beeng@discuss.tchncs.de 4 weeks ago
Not my server, it’s a shared one I have a http server and some files on. I want a nice frontend. I’ve used all in one php ones with some success, but this looks nicer.
Darkassassin07@lemmy.ca 4 weeks ago
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.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.
victorz@lemmy.world 4 weeks ago
Man that’s finicky…
MangoPenguin@lemmy.blahaj.zone 4 weeks ago
It’s just YAML, if you do
FILEBROWSER_CONFIG:“/config/config.yaml”
instead it might work with quotes.Darkassassin07@lemmy.ca 4 weeks ago
Dev replied to my github discussion.
Apparently it’s an issue with array style env variable layout.
Instead of