From c309276f1dc2b853c779f872166ca69979c3f84b Mon Sep 17 00:00:00 2001 From: librelad Date: Tue, 26 May 2026 16:16:25 +0100 Subject: [PATCH] feat(backup): also label focalboard (consistent with the same overlap pattern) MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit I skipped focalboard earlier citing "DB+files overlap" (sqlite lives in the same dir as the file-capture target). But linkding / vaultwarden / headscale all have that exact same shape and we just labeled them in 12b4d68. gitea has had it for ages and it's proven — the DB dump excludes the raw .db from the snapshot, the file-capture grabs the dir (incl. live sqlite), and restore replays the dump over the captured tree. The torn live-sqlite copy is harmless bloat. So focalboard gets the same treatment for consistency. Coverage now: 9 apps (adguard set aside, jellyfin still pending DB declaration). Co-Authored-By: Claude Opus 4.7 Signed-off-by: librelad --- containers/focalboard/docker-compose.yml | 1 + 1 file changed, 1 insertion(+) diff --git a/containers/focalboard/docker-compose.yml b/containers/focalboard/docker-compose.yml index eaccfec..29ee121 100755 --- a/containers/focalboard/docker-compose.yml +++ b/containers/focalboard/docker-compose.yml @@ -23,6 +23,7 @@ services: libreportal.category: "CATEGORY_DATA" #LIBREPORTAL|CATEGORY_TAG|CATEGORY_DATA libreportal.title: "TITLE_DATA" #LIBREPORTAL|TITLE_TAG|TITLE_DATA libreportal.backup.db: "sqlite:::data/focalboard.db" + libreportal.backup.files: "focalboard-service:/opt/focalboard/data:data" traefik.enable: TRAEFIK_ENABLE_DATA #LIBREPORTAL|TRAEFIK_ENABLE_TAG|TRAEFIK_ENABLE_DATA # TRAEFIK_PORT_1_BEGIN traefik.http.routers.focalboard-service.entrypoints: web,websecure