meta-core claims model: pin meta-core 2.0.1, meta-read 1.4.1, meta-watch 1.1.0, meta-search 1.3.2, meta-share 2.7.0, gateway 1.1.1, meta-sort 1.1.1, plugins 1.1.0; signing keys + db-cache backup exclude

Apps/MetaWatchShared/docker-compose.yml

@@ -45,7 +45,7 @@ services:
   # core of its own.
   # ---------------------------------------------------------------------------
   metawatch-search:
-    image: ipcr-watch.nsl.sh/ipns/metadec.eth/metadec.eth/meta-search:1.2.10
+    image: ipcr-watch.nsl.sh/ipns/metadec.eth/metadec.eth/meta-search:1.3.2
     container_name: metawatch-search
     hostname: metawatch-search
     restart: unless-stopped
@@ -71,6 +71,9 @@ services:
       # swarm. Without this mount both are on the container's writable layer and
       # every image bump loses the prefs and re-fetches every poster.
       - ${DATA_ROOT:-/DATA}/AppData/metawatch/search-data:/data:rw
+      # Claim-signing keys (meta-core 2.0.0 claims model), one file per writer
+      # service in this stack. Config — backed up, NOT in backup.exclude.
+      - ${DATA_ROOT:-/DATA}/AppData/metawatch/keys:/keys:rw
     environment:
       P2P_LISTEN: "/ip4/0.0.0.0/tcp/4001"
       # Public IPFS DHT bootstraps by explicit /dns4/.../tcp/4001 (the nested
@@ -93,6 +96,8 @@ services:
       META_CORE_URL: "http://metacore-app:80"
       BASE_URL: "http://metawatch-search:3000"
       INTERNAL_BASE_URL: "http://metawatch-search:3000"
+      # Own claim-signing key (relayed claims are forwarded verbatim, never re-signed); generated on first boot if missing.
+      METAMESH_SIGNING_KEY_FILE: "/keys/metawatch-search.key"
       TZ: "$TZ"
     healthcheck:
       test: ["CMD", "curl", "-sf", "http://localhost:3000/health"]
@@ -115,7 +120,7 @@ services:
   # owns the caddy_* labels directly and Caddy proxies straight to :3000.
   # ---------------------------------------------------------------------------
   metawatch-app:
-    image: ipcr-watch.nsl.sh/ipns/metadec.eth/metadec.eth/meta-watch:1.0.93
+    image: ipcr-watch.nsl.sh/ipns/metadec.eth/metadec.eth/meta-watch:1.1.0
     container_name: metawatch-app
     hostname: metawatch-app
     restart: unless-stopped
@@ -130,6 +135,9 @@ services:
       - 3000
     volumes:
       - ${DATA_ROOT:-/DATA}/AppData/metawatch/data:/app/data
+      # Claim-signing keys (meta-core 2.0.0 claims model), one file per writer
+      # service in this stack. Config — backed up, NOT in backup.exclude.
+      - ${DATA_ROOT:-/DATA}/AppData/metawatch/keys:/keys:rw
     environment:
       # The STANDALONE MetaShare app — this variant ships no transport peer.
       META_SHARE_URL: "http://metashare-app:3000"
@@ -143,6 +151,8 @@ services:
       # variant has no private core: it writes to the standalone MetaCore app,
       # which already mounts /files and runs the watcher.
       META_CORE_URL: "http://metacore-app:80"
+      # Own claim-signing key for the subtitle-store claims it writes; generated on first boot if missing.
+      METAMESH_SIGNING_KEY_FILE: "/keys/metawatch-app.key"
       TZ: "$TZ"
     depends_on:
       metawatch-search:
@@ -197,7 +207,7 @@ services:
       BACKEND_HOST: "metawatch-search"
       BACKEND_PORT: "3000"
       LISTEN_PORT: "80"
-      REDIRECT_HOST_SUFFIXES: "${APP_DOMAIN},${APP_PUBLIC_IP_DASH}.${APP_IP_ZONE},${APP_PUBLIC_IP_DASH}.sslip.io"
+      REDIRECT_HOST_SUFFIXES: "${APP_HOST_SUFFIXES:-${APP_DOMAIN},${APP_PUBLIC_IP_DASH}.${APP_IP_ZONE},${APP_PUBLIC_IP_DASH}.sslip.io}"
     depends_on:
       - metawatch-search
     labels:
@@ -346,6 +356,9 @@ x-compose-app:
     - path: /DATA/AppData/metawatch/data
       user: $PUID
       group: $PGID
+    - path: /DATA/AppData/metawatch/keys
+      user: $PUID
+      group: $PGID
   # Same string as the caddy_0 label, so the tile link and the route agree.
   webui-host: metawatch-${domain}
   webui-path: "/"