fix: SyncFileBrowserMounts reads domain from controller config instead of missing .env
The filebrowser stack has no .env file — domain is baked into compose labels by docker-setup.sh. The sync always bailed with a WARN and storage paths were never applied to FileBrowser's config.yaml or docker-compose.yml. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
This commit is contained in:
@@ -1,5 +1,10 @@
|
||||
## Changelog
|
||||
|
||||
### v0.27.1 — Fix FileBrowser Mount Sync (2026-02-22)
|
||||
|
||||
#### Fixed
|
||||
- **`internal/web/handlers.go`** — `SyncFileBrowserMounts()` was reading the domain from a `.env` file that doesn't exist in the filebrowser stack directory (domain is baked into the compose labels by `docker-setup.sh`). It always logged `[WARN] Cannot read DOMAIN from FileBrowser .env — skipping mount sync` and returned early, so storage paths were never synced to FileBrowser's config.yaml or docker-compose.yml. Fixed by using `s.cfg.Customer.Domain` directly from the controller config.
|
||||
|
||||
### v0.27.0 — User-Configurable App Subdomains (2026-02-22)
|
||||
|
||||
#### Added
|
||||
|
||||
Reference in New Issue
Block a user