feat: Dockerfile, deploy configs en Caddy-block voor ops.jp-visser.nl

- Multi-stage Dockerfile (deps → builder → runner) met next standalone output
- .dockerignore zodat node_modules en .next niet mee worden gebundeld
- next.config.ts: output standalone ingeschakeld voor minimale image
- deploy/docker-compose.ops-dashboard.yml: service-fragment voor /srv/scrum4me/compose
- deploy/caddy/Caddyfile.ops-dashboard: reverse_proxy block voor Caddy
- deploy/ops-dashboard.env.example: env-template voor /srv/ops/ops-dashboard.env

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>

deploy/docker-compose.ops-dashboard.yml

@@ -0,0 +1,19 @@
+# Fragment to merge into /srv/scrum4me/compose/docker-compose.yml
+# Add the ops-dashboard service under the `services:` key.
+#
+# Build the image first:
+#   docker build -t ops-dashboard /srv/ops/ops-dashboard
+#
+# Then bring the service up:
+#   docker compose -f /srv/scrum4me/compose/docker-compose.yml up -d ops-dashboard
+
+services:
+  ops-dashboard:
+    build:
+      context: /srv/ops/ops-dashboard
+    env_file: /srv/ops/ops-dashboard.env
+    ports:
+      - "127.0.0.1:3001:3000"
+    restart: unless-stopped
+    depends_on:
+      - postgres