Comment on PSA: filebrowser is no longer being actively developed

<- View Parent
Darkassassin07@lemmy.ca ⁨4⁩ ⁨days⁩ 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.

source
Sort:hotnewtop