Upgrade to 1.1.1-stable and normal user weer

normale user om geen andere problemen te voorkomen. Ik fix het wel in het rsync command dat uploaden niet werkte
Bump
2026-01-13 21:47:06 +01:00 · 2026-01-13 21:33:49 +01:00 · 2026-01-13 21:32:52 +01:00 · 2026-01-11 19:35:13 +01:00 · 2026-01-11 18:26:11 +01:00 · 2026-01-11 18:13:44 +01:00
3 changed files with 19 additions and 6 deletions
--- a/my-filebrowser-quantum/data/config.yaml
+++ b/my-filebrowser-quantum/data/config.yaml
@@ -1,6 +1,6 @@
 server:
  port: 80
-  database: "./database/database.db"
+  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"
@@ -28,6 +28,19 @@ integrations:
    url: "https://onlyoffice.c01242a0-c0cf-4799-a47e-52e891963e28.nl"
    secret: "<Plak hier de JWT-secret van OnlyOffice.>"

+userDefaults:
+  editorQuickSave: true # show quick save button in editor
+  singleClick: true # open directory on single click, also enables middle click to open in new tab
+  permissions:
+    api: false # allow api access
+    admin: false # allow admin access
+    modify: true # allow modifying files
+    share: true # allow sharing files
+    realtime: true # allow realtime updates
+    delete: true # allow deleting files
+    create: true # allow creating or uploading files
+    download: true # allow downloading files
+
 frontend:
  name: "Home Drive"
  description: "Zoals Google Drive maar dan zelfgehost"
--- a/my-filebrowser-quantum/docker-compose.yml
+++ b/my-filebrowser-quantum/docker-compose.yml
@@ -7,10 +7,10 @@ services:
      APP_PORT: 80

  web:
-    image: ghcr.io/gtsteffaniak/filebrowser:1.1.0-stable@sha256:3db0a5ebde84ff1de72c93f776495089e79f3e710e931687c1a720c162e32a20
+    image: ghcr.io/gtsteffaniak/filebrowser:1.1.1-stable@sha256:aa6d214d269af8785f6af7c1bb3d2cda019a09265b3d3bdff22257e9dc993ee4
    restart: on-failure
    environment:
-      FILEBROWSER_CONFIG: "data/config.yaml" # overrides the default path which is ./config.yaml
+      FILEBROWSER_CONFIG: "/home/filebrowser/data/config.yaml"
    volumes:
      - ${UMBREL_ROOT}/data/storage:/storage
-      - ${APP_DATA_DIR}/data/:/home/filebrowser/data
+      - ${APP_DATA_DIR}/data/:/home/filebrowser/data:rw
--- a/my-filebrowser-quantum/umbrel-app.yml
+++ b/my-filebrowser-quantum/umbrel-app.yml
@@ -4,7 +4,7 @@ name: FileBrowser Quantum
 tagline: The best free self-hosted web-based file manager
 icon: https://filebrowserquantum.com/logo.svg
 category: MyApps
-version: "1.1.0"
+version: "1.1.1"
 port: 8633
 description: >-
  FileBrowser Quantum provides an easy way to access and manage your files from the web. It has a modern responsive interface that has many advanced features to manage users, access, sharing, and file preview and editing.
@@ -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 17:47
+  This update brings all 1.1.4 beta changes to stable. Laatste wijziging: 2025-01-13 21:45
 dependencies:
 path: ""
 defaultUsername: ""
Author	SHA1	Message	Date
Christiaan Westerbeek	9fe65d51a0	Upgrade to 1.1.1-stable and normal user weer normale user om geen andere problemen te voorkomen. Ik fix het wel in het rsync command dat uploaden niet werkte	2026-01-13 21:47:06 +01:00
Christiaan Westerbeek	da1a0af525	Bump	2026-01-13 21:33:49 +01:00
Christiaan Westerbeek	d12072d6a9	Fixen dat nieuwe directories umbrel:umbrel krijgen bij aanmaak via FileBrowser Quantum net zoals via aanmaak Umbrel Files	2026-01-13 21:32:52 +01:00
Christiaan Westerbeek	e65d518c63	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.	2026-01-11 19:35:13 +01:00
Christiaan Westerbeek	1be9234feb	Hopelijk wordt zo database.md ook op local file system persist	2026-01-11 18:26:11 +01:00
Christiaan Westerbeek	2e31ab88c4	database wordt weer hergecreeerd na elke restart	2026-01-11 18:13:44 +01:00