fix: align ProxCenter Postgres NFS ownership

proxcenter-compose.yml

@@ -52,7 +52,7 @@ services:
       # - APP_SECRET_FILE=/run/secrets/app_secret
       # - NEXTAUTH_SECRET_FILE=/run/secrets/nextauth_secret
     volumes:
-      - ${DockerData}/proxcenter/frontend_data:/app/data
+      - ${DockerData:-/mnt/DockerStorage/data}/proxcenter/frontend_data:/app/data
     # secrets:
     #   - app_secret
     #   - nextauth_secret
@@ -92,9 +92,10 @@ services:
   # ========================================
   postgres:
     image: postgres:16-alpine
-    # Run as the postgres UID/GID used by postgres:16-alpine so the NFS-backed
-    # data directory can be owned by 70:70 on TrueNAS and avoid startup chown failures.
-    user: "70:70"
+    # Run as the numeric owner seen through Wheelz's NFS mount. On this Swarm,
+    # TrueNAS maps the ProxCenter Postgres data directory to 3003:999 from the
+    # containers' perspective; running Postgres as 70:70 causes "wrong ownership".
+    user: "3003:999"
     environment:
       - POSTGRES_USER=${POSTGRES_USER:-proxcenter}
       - POSTGRES_PASSWORD=${POSTGRES_PASSWORD}
@@ -103,7 +104,7 @@ services:
     volumes:
       # Mount the pre-created pgdata directory directly. This avoids Postgres
       # needing to create/chmod a child directory on the NFS mount root.
-      - ${DockerData}/proxcenter/postgres_data/pgdata:/var/lib/postgresql/data
+      - ${DockerData:-/mnt/DockerStorage/data}/proxcenter/postgres_data/pgdata:/var/lib/postgresql/data
     # Port is intentionally not published. Postgres is reachable only
     # over the internal overlay network. Uncomment to expose for debugging:
     # ports: