Hello! I have stepped down from this project a long time ago, and @o1egl has been maintaining it for years. However, none of us have as much time as we used to have to maintain this project, especi...
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:
/srv/filebrowser-new/data:/config
environment:
FILEBROWSER_CONFIG=“/config/config.yaml”
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…
https://github.com/gtsteffaniak/filebrowser
File browser Quantum is the shiny feature rich fork
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…
It’s just YAML, if you do
FILEBROWSER_CONFIG:"/config/config.yaml"instead it might work with quotes.When the stable release is published, it’s honestly a no brainer. Although Filestash is a good alternative too.