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.
