CI: fix deploy failures — pin compose project name in docker-compose.yml, drop COMPOSE_PROJECT_NAME=osint override (would orphan osint-dashboard_osint-pgdata); runner now mounts cli-plugins so 'docker compose' works in job containers

.forgejo/workflows/build.yml

@@ -9,19 +9,19 @@ jobs:
       - name: Checkout
         uses: https://code.forgejo.org/actions/checkout@v4
       - name: Build and deploy on the Pi (local docker)
-        env:
-          # force a stable compose project name so container names stay
-          # consistent (osint-app, osint-db, ...) regardless of checkout path
-          COMPOSE_PROJECT_NAME: osint
         run: |
           set -ex
           # The forgejo-runner runs on the Pi with /var/run/docker.sock and
           # /opt/siriusdevops mounted, so we build + deploy LOCALLY — no SSH/scp.
           # Deploy straight from the checked-out workspace.
           cd "${GITHUB_WORKSPACE}"
+          # Project name is pinned by `name:` in docker-compose.yml
+          # (osint-dashboard), matching the live volume
+          # osint-dashboard_osint-pgdata. Do NOT override COMPOSE_PROJECT_NAME
+          # here — a different name would create a fresh empty pgdata volume.
           docker compose build --no-cache
           docker compose up -d --force-recreate
           docker image prune -f
           echo 'osint-dashboard deployed (local)'
 
-# deployed locally on the Pi via runner (docker socket + /opt/siriusdevops mounted)
+# deployed locally on the Pi via runner (docker socket + cli-plugins mounted)

docker-compose.yml

@@ -6,6 +6,11 @@
 # Bring up:   docker compose up -d
 # With NATS:  docker compose --profile ingest up -d
 # Env:        copy .env.example to .env and adjust.
+#
+# Project name is pinned here (NOT via COMPOSE_PROJECT_NAME in CI) so the
+# named volumes stay osint-dashboard_osint-pgdata / _camera-snapshots and
+# match the live stack on the Pi.
+name: osint-dashboard
 
 services:
   db: