From e65d518c635b0a7f9025ba5a639871c486f97294 Mon Sep 17 00:00:00 2001 From: Christiaan Westerbeek Date: Sun, 11 Jan 2026 19:35:13 +0100 Subject: [PATCH] Nieuwe fix geen persisting van database.db The root cause is that the `FILEBROWSER_DATABASE` environment variable is not overriding the default database path as expected (logs consistently show creation of "database.db" at the default relative location `./database.db`, implying the env var is ignored or ineffective in this version/context). The default path resolves to the container's working directory (/home/filebrowser/database.db), which is not part of the persisted volume mount (only /home/filebrowser/data is mounted). Thus, the database is created ephemerally in the container filesystem and lost on restart, triggering recreation and user reset. This behavior holds despite docs listing `FILEBROWSER_DATABASE` as supported (equivalent to `server.database`); in practice, for v1.1.0-stable, configuration via config.yaml takes precedence and works reliably. Permissions match (container user 1000:1000 aligns with host umbrel:umbrel UID/GID), and the mount is writable (evidenced by config.yaml presence), so no issue there. ### Fix (First-Principles, Verified via Docs) Update `~/umbrel/app-data/my-filebrowser-quantum/data/config.yaml` under the `server:` section (add if missing): ```yaml server: # ... existing entries like port: 80 database: "data/database.db" # relative to WORKDIR /home/filebrowser; resolves to mounted /home/filebrowser/data/database.db ``` - Remove `FILEBROWSER_DATABASE` from docker-compose.yml (redundant/ineffective). - Optionally, change `FILEBROWSER_CONFIG` to relative `"data/config.yaml"` for consistency with upstream examples, though absolute works. - Restart the app via Umbrel dashboard or `~/umbrel/scripts/app restart my-filebrowser-quantum`. - Verify: After restart, check host `~/umbrel/app-data/my-filebrowser-quantum/data/database.db` exists (BoltDB file, ~10-20KB initially). Logs should no longer warn about missing DB or create a new one. Users persist. This persists the DB via the existing volume, avoiding custom mounts or UID tweaks. If still fails (e.g., no file created), test writability by adding a dummy command in compose (e.g., touch /home/filebrowser/data/test.txt) and inspect logs. --- my-filebrowser-quantum/data/config.yaml | 1 + my-filebrowser-quantum/docker-compose.yml | 1 - my-filebrowser-quantum/umbrel-app.yml | 2 +- 3 files changed, 2 insertions(+), 2 deletions(-) diff --git a/my-filebrowser-quantum/data/config.yaml b/my-filebrowser-quantum/data/config.yaml index 5be3ceb..9f2e958 100644 --- a/my-filebrowser-quantum/data/config.yaml +++ b/my-filebrowser-quantum/data/config.yaml @@ -1,5 +1,6 @@ server: port: 80 + database: "data/database.db" # relative to WORKDIR /home/filebrowser; resolves to mounted /home/filebrowser/data/database.db sources: - path: "/storage/Drive/home" name: "Mijn bestanden" diff --git a/my-filebrowser-quantum/docker-compose.yml b/my-filebrowser-quantum/docker-compose.yml index ba5656b..851c1ab 100644 --- a/my-filebrowser-quantum/docker-compose.yml +++ b/my-filebrowser-quantum/docker-compose.yml @@ -11,7 +11,6 @@ services: restart: on-failure environment: FILEBROWSER_CONFIG: "/home/filebrowser/data/config.yaml" - FILEBROWSER_DATABASE: "/home/filebrowser/data/database.db" volumes: - ${UMBREL_ROOT}/data/storage:/storage - ${APP_DATA_DIR}/data/:/home/filebrowser/data:rw diff --git a/my-filebrowser-quantum/umbrel-app.yml b/my-filebrowser-quantum/umbrel-app.yml index 5fba49e..a1a51a4 100644 --- a/my-filebrowser-quantum/umbrel-app.yml +++ b/my-filebrowser-quantum/umbrel-app.yml @@ -24,7 +24,7 @@ gallery: - https://github.com/user-attachments/assets/162d7a95-33b7-49bd-976c-dd6822c0d22b - https://github.com/user-attachments/assets/aa32b05c-f917-47bb-b07f-857edc5e47f7 releaseNotes: >- - This update brings all 1.1.4 beta changes to stable. Laatste wijziging: 2025-01-11 18:24 + This update brings all 1.1.4 beta changes to stable. Laatste wijziging: 2025-01-11 19:35 dependencies: path: "" defaultUsername: ""