fix: FileBrowser reads stale config on fresh deployments
The gtstef/filebrowser image bakes FILEBROWSER_CONFIG=/home/filebrowser/data/config.yaml, but controller mounts config at /home/filebrowser/config.yaml. Override the env var in both generateFileBrowserCompose() and docker-setup.sh so FileBrowser reads the controller-managed config with proper sources and database path. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
This commit is contained in:
@@ -1304,6 +1304,7 @@ services:
|
||||
restart: unless-stopped
|
||||
environment:
|
||||
- TZ=Europe/Budapest
|
||||
- FILEBROWSER_CONFIG=/home/filebrowser/config.yaml
|
||||
volumes:
|
||||
- filebrowser_data:/home/filebrowser/data
|
||||
- ./config.yaml:/home/filebrowser/config.yaml:ro
|
||||
|
||||
Reference in New Issue
Block a user