Dashrendar2507

Hi! Thanks for the template. I was able to get it to work, but I have a question. Currently, we are asked to create the config.yaml in /home/filebrowser/data (container path). However, after boot, a database and config file will be automatically created at /home/filebrowser/data (notice the lack of "data" folder). When making changes in the app, only the config in /home/filebrowser/ will be modified, NOT the one we mapped the path. Of course, the easiest solution would be to map the host to /home/filebrowser/, but doing this gives me an error, because it overrides the container's filesystem, which is required to boot the app in the first place (it runs ./filebrowser). Now, here is what I did to get it to work correctly - I just don't know if it's going to work well with future updates. Start the container with the default settings, which will create the duplicated files in /home/filebrowser/. Use the container's console to copy all the files an folders from /home/filebrowser/ to /home/filebrowser/data (your mapped path) using this commands: cp -r -f /home/filebrowser/filebrowser /home/filebrowser/data cp -r -f /home/filebrowser/http /home/filebrowser/data Here, the -r is for reccursive (the http folder won't work otherwise). Once that's done, you should see these files on your host's mapped path. Stop the FileBrowser container and edit it. Change your paths to remove "/data" in the container paths. So, for example, replace all instances of "/home/filebrowser/data" with "/home/filebrowser". Make the necessary edits to your config.yaml so that the paths point to the correct database and tmp folders (I highly recommend using full paths, ie "/home/filebrowser/database.db" to avoid confusion). Re-execute the chown and chmod commands from the "Additional Requirements" section of the template. Restart the container. Check the logs - all should be normal. What we did here is map the paths correctly and ensure that the mapped folder has the required scripts for FileBrowser to start. Feel free to make changes to your settings in the app, and you should now see your mapped config.yaml be properly updated.