feat: platform backbone and field capture, first part (checkpoint)

Platform backbone (plan 2026-10-13-plattform-rueckgrat), reviewed tasks:
- run roles api/worker/job/all with shared startup checks (Task 1)
- schema and migration for DomainEvent, deliveries, JobRun, ThrottlerHit (Task 2)
- audit, notifications and domain events written in the same transaction (Task 3)
- dispatcher with SKIP LOCKED claims, retries and stale release (Task 4)
- worker building blocks: tick, LISTEN/NOTIFY wake-up, health (Task 5)
- worker process and entry points (Task 6)
- throttler counters in Postgres (Task 19)
- separate keys per purpose with key ring (Task 20)
- public origin page without exact location (Task 22)
- shop keys split into read and write (Task 23)
- Kustomize base, components, overlay encry, CI validation (Task 26)

Field capture T3 (plan 2026-10-13-t3-erfassung-am-stand), reviewed tasks:
- brood frames, read endpoints, apiary overview and offline pack
- network basics, offline queue v3, navigation sheets, form building blocks
- new inspection with last-time hints and weather, varroa per day,
  treatment prefill, apiary page with round
- inspection photo (Task 10) is implemented, review pending

Not rolled out. Remaining tasks follow in later commits.

Co-Authored-By: Claude Opus 5.5 (1M context) <[email protected]>
This commit is contained in:
Nick SzaunigandClaude Opus 5.5 committed 2026-10-13 17:57:54 +02:00
1 parent 10cbe9bf2d
commit c01a38835a
340 files changed
+25695 -1808

No files matched your search

@@ -0,0 +1,163 @@
# job-Rolle: je Job ein CronJob `node dist/cli.js <job>` (Spec 2026-10-12
# Abschnitt 2). Hier steht nur, was je Job verschieden ist. Zeitzone,
# Forbid, Aufbewahrung, Image, Umgebung, Haertung und Ressourcen setzt der
# gemeinsame Patch in kustomization.yaml fuer alle CronJobs mit
# app=apicore-job.
apiVersion: batch/v1
kind: CronJob
metadata:
name: apicore-job-cleanup
labels:
app: apicore-job
apicore.io/job: cleanup
spec:
schedule: "0 4 * * *"
jobTemplate:
spec:
backoffLimit: 1
activeDeadlineSeconds: 1800
template:
metadata:
labels:
app: apicore-job
apicore.io/job: cleanup
db-client: "true"
spec:
containers:
- name: job
command: ["node", "dist/cli.js", "cleanup"]
---
apiVersion: batch/v1
kind: CronJob
metadata:
name: apicore-job-daily-evaluation
labels:
app: apicore-job
apicore.io/job: daily-evaluation
spec:
schedule: "30 4 * * *"
jobTemplate:
spec:
backoffLimit: 1
activeDeadlineSeconds: 1800
template:
metadata:
labels:
app: apicore-job
apicore.io/job: daily-evaluation
db-client: "true"
spec:
containers:
- name: job
command: ["node", "dist/cli.js", "daily-evaluation"]
---
apiVersion: batch/v1
kind: CronJob
metadata:
name: apicore-job-task-templates
labels:
app: apicore-job
apicore.io/job: task-templates
spec:
schedule: "0 5 * * *"
jobTemplate:
spec:
backoffLimit: 1
activeDeadlineSeconds: 1800
template:
metadata:
labels:
app: apicore-job
apicore.io/job: task-templates
db-client: "true"
spec:
containers:
- name: job
command: ["node", "dist/cli.js", "task-templates"]
---
# Laeuft stuendlich und prueft selbst, ob laut Zeitplan aus GUI oder Env
# ein Backup faellig ist. Schreibt nach /data/backups (apicore-data) und
# liest die Dokumente aus /data/documents.
apiVersion: batch/v1
kind: CronJob
metadata:
name: apicore-job-app-backup
labels:
app: apicore-job
apicore.io/job: app-backup
spec:
schedule: "0 * * * *"
jobTemplate:
spec:
backoffLimit: 0
activeDeadlineSeconds: 3600
template:
metadata:
labels:
app: apicore-job
apicore.io/job: app-backup
db-client: "true"
spec:
volumes:
- name: data
persistentVolumeClaim:
claimName: apicore-data
containers:
- name: job
command: ["node", "dist/cli.js", "app-backup"]
volumeMounts:
- name: data
mountPath: /data
---
# rekey und rekey-dry-run laufen nie nach Zeitplan (suspend, 31. Februar),
# nur von Hand: kubectl create job ... --from=cronjob/apicore-job-rekey
# (Runbook Schritt 4).
apiVersion: batch/v1
kind: CronJob
metadata:
name: apicore-job-rekey
labels:
app: apicore-job
apicore.io/job: rekey
spec:
schedule: "0 0 31 2 *"
suspend: true
jobTemplate:
spec:
backoffLimit: 0
activeDeadlineSeconds: 1800
template:
metadata:
labels:
app: apicore-job
apicore.io/job: rekey
db-client: "true"
spec:
containers:
- name: job
command: ["node", "dist/cli.js", "rekey"]
---
apiVersion: batch/v1
kind: CronJob
metadata:
name: apicore-job-rekey-dry-run
labels:
app: apicore-job
apicore.io/job: rekey-dry-run
spec:
schedule: "0 0 31 2 *"
suspend: true
jobTemplate:
spec:
backoffLimit: 0
activeDeadlineSeconds: 1800
template:
metadata:
labels:
app: apicore-job
apicore.io/job: rekey-dry-run
db-client: "true"
spec:
containers:
- name: job
command: ["node", "dist/cli.js", "rekey", "--dry-run"]
@@ -0,0 +1,71 @@
# Laufrollen aus einem Image (Spec 2026-10-12 Abschnitt 2): api (Patch auf
# apicore-backend), worker (eigenes Deployment) und job (CronJobs).
# Rollout: Runbook Schritt 3, erst nachdem das Secret die neuen Schluessel hat.
apiVersion: kustomize.config.k8s.io/v1alpha1
kind: Component
resources:
- worker-deployment.yaml
- cronjobs.yaml
patches:
- path: patch-api.yaml
# Gemeinsam fuer alle App-CronJobs; cronjobs.yaml haelt nur, was je Job
# verschieden ist. Werte laut Plan 2026-10-13 "Global Constraints".
- target:
kind: CronJob
labelSelector: app=apicore-job
patch: |-
apiVersion: batch/v1
kind: CronJob
metadata:
name: any-app-job
spec:
timeZone: Europe/Berlin
concurrencyPolicy: Forbid
startingDeadlineSeconds: 600
successfulJobsHistoryLimit: 3
failedJobsHistoryLimit: 3
jobTemplate:
spec:
ttlSecondsAfterFinished: 86400
template:
spec:
restartPolicy: Never
automountServiceAccountToken: false
securityContext:
runAsNonRoot: true
runAsUser: 1000
runAsGroup: 1000
seccompProfile:
type: RuntimeDefault
volumes:
- name: tmp
emptyDir: {}
containers:
- name: job
image: git.encry.de/nick.rosenloecher/apicore-backend
imagePullPolicy: IfNotPresent
env:
- name: APICORE_ROLE
value: job
- name: HOME
value: /tmp
envFrom:
- configMapRef:
name: apicore-backend-config
- secretRef:
name: apicore-backend-secret
securityContext:
allowPrivilegeEscalation: false
readOnlyRootFilesystem: true
capabilities:
drop: ["ALL"]
volumeMounts:
- name: tmp
mountPath: /tmp
resources:
requests:
cpu: 50m
memory: 192Mi
limits:
cpu: 500m
memory: 512Mi
@@ -0,0 +1,91 @@
# api-Rolle des Backends (Spec 2026-10-12 Abschnitte 2, 5.3 und 7).
# Migration und Seed laufen als initContainer statt im CMD: scheitert die
# Migration, startet der neue Pod nicht und der alte laeuft weiter.
# `migrate deploy` nimmt einen Advisory-Lock in der DB, darum duerfen api und
# worker gleichzeitig starten. Den Seed fuehrt nur die api aus.
apiVersion: apps/v1
kind: Deployment
metadata:
name: apicore-backend
spec:
template:
# Das Label db-client: "true" setzt components/network-policies, deren
# Postgres-Policy es braucht.
spec:
automountServiceAccountToken: false
volumes:
- name: tmp
emptyDir: {}
initContainers:
- name: migrate
image: git.encry.de/nick.rosenloecher/apicore-backend
imagePullPolicy: IfNotPresent
command: ["node", "node_modules/prisma/build/index.js", "migrate", "deploy"]
env:
- name: HOME
value: /tmp
- name: CHECKPOINT_DISABLE
value: "1"
envFrom:
- configMapRef:
name: apicore-backend-config
- secretRef:
name: apicore-backend-secret
securityContext:
allowPrivilegeEscalation: false
readOnlyRootFilesystem: true
capabilities:
drop: ["ALL"]
volumeMounts:
- name: tmp
mountPath: /tmp
resources:
requests:
cpu: 50m
memory: 192Mi
limits:
cpu: 500m
memory: 512Mi
- name: seed
image: git.encry.de/nick.rosenloecher/apicore-backend
imagePullPolicy: IfNotPresent
command: ["node", "dist/seed.js"]
envFrom:
- configMapRef:
name: apicore-backend-config
- secretRef:
name: apicore-backend-secret
securityContext:
allowPrivilegeEscalation: false
readOnlyRootFilesystem: true
capabilities:
drop: ["ALL"]
volumeMounts:
- name: tmp
mountPath: /tmp
resources:
requests:
cpu: 50m
memory: 192Mi
limits:
cpu: 500m
memory: 512Mi
containers:
- name: apicore-backend
env:
- name: APICORE_ROLE
value: api
- name: HOME
value: /tmp
securityContext:
readOnlyRootFilesystem: true
volumeMounts:
- name: tmp
mountPath: /tmp
resources:
requests:
cpu: 50m
memory: 192Mi
limits:
cpu: 500m
memory: 512Mi
@@ -0,0 +1,127 @@
# worker-Rolle: Event-Dispatcher, Kalender-Outbox und Webhook-Zustellung
# (Spec 2026-10-12 Abschnitt 2). Kein Service und kein Ingress; Port 3002
# beantwortet nur /health fuer die Probes. Alle Schleifen arbeiten mit
# SKIP LOCKED, mehr als ein Replica waere also moeglich.
apiVersion: apps/v1
kind: Deployment
metadata:
name: apicore-worker
labels:
app: apicore-worker
spec:
replicas: 1
# Wie bei der api: scheitert die Migration, laeuft der alte Worker weiter.
strategy:
type: RollingUpdate
rollingUpdate:
maxSurge: 1
maxUnavailable: 0
selector:
matchLabels:
app: apicore-worker
template:
metadata:
labels:
app: apicore-worker
db-client: "true"
spec:
automountServiceAccountToken: false
terminationGracePeriodSeconds: 30
securityContext:
runAsNonRoot: true
runAsUser: 1000
runAsGroup: 1000
seccompProfile:
type: RuntimeDefault
volumes:
- name: tmp
emptyDir: {}
initContainers:
# Ohne Seed: den fuehrt nur die api aus.
- name: migrate
image: git.encry.de/nick.rosenloecher/apicore-backend
imagePullPolicy: IfNotPresent
command: ["node", "node_modules/prisma/build/index.js", "migrate", "deploy"]
env:
- name: HOME
value: /tmp
- name: CHECKPOINT_DISABLE
value: "1"
envFrom:
- configMapRef:
name: apicore-backend-config
- secretRef:
name: apicore-backend-secret
securityContext:
allowPrivilegeEscalation: false
readOnlyRootFilesystem: true
capabilities:
drop: ["ALL"]
volumeMounts:
- name: tmp
mountPath: /tmp
resources:
requests:
cpu: 50m
memory: 192Mi
limits:
cpu: 500m
memory: 512Mi
containers:
- name: apicore-worker
image: git.encry.de/nick.rosenloecher/apicore-backend
imagePullPolicy: IfNotPresent
command: ["node", "dist/worker.js"]
env:
- name: APICORE_ROLE
value: worker
- name: WORKER_HEALTH_PORT
value: "3002"
- name: HOME
value: /tmp
envFrom:
- configMapRef:
name: apicore-backend-config
- secretRef:
name: apicore-backend-secret
ports:
- name: health
containerPort: 3002
securityContext:
allowPrivilegeEscalation: false
readOnlyRootFilesystem: true
capabilities:
drop: ["ALL"]
volumeMounts:
- name: tmp
mountPath: /tmp
# /health ist gesund, wenn die DB in hoechstens 5 s antwortet und
# der letzte Dispatcher-Durchlauf hoechstens 2 Minuten her ist.
# Darum timeoutSeconds 5 statt der Vorgabe von 1 s.
startupProbe:
httpGet:
path: /health
port: health
failureThreshold: 30
periodSeconds: 10
timeoutSeconds: 5
livenessProbe:
httpGet:
path: /health
port: health
periodSeconds: 30
failureThreshold: 3
timeoutSeconds: 5
readinessProbe:
httpGet:
path: /health
port: health
periodSeconds: 15
timeoutSeconds: 5
resources:
requests:
cpu: 20m
memory: 128Mi
limits:
cpu: 200m
memory: 256Mi