feat(jarrs): add run-migrations initContainer to dev deployment

Runs node apps/api/dist/migrate.js after wait-for-db and wait-for-redis, applying Drizzle SQL migrations before the API starts. Fixes fresh deployment failing with "relation does not exist". Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
2026-03-04 09:37:01 +01:00
parent 0c1fbc7410
commit 9c0cfec113
1 changed files with 33 additions and 0 deletions
@@ -332,6 +332,39 @@ spec:
                sleep 2
              done
              echo "Redis is ready!"
        - name: run-migrations
          image: gitea.dooplex.hu/admin/jarr:latest
          imagePullPolicy: Always
          command: ["node", "apps/api/dist/migrate.js"]
          env:
            - name: NODE_ENV
              value: development
            - name: DB_USER
              valueFrom:
                secretKeyRef:
                  name: dev-jarr-db
                  key: username
            - name: DB_PASS
              valueFrom:
                secretKeyRef:
                  name: dev-jarr-db
                  key: password
            - name: DATABASE_URL
              value: "postgresql://$(DB_USER):$(DB_PASS)@dev-jarr-postgres:5432/jarr_dev"
            - name: REDIS_URL
              value: "redis://dev-jarr-redis:6379"
            - name: JWT_ACCESS_SECRET
              valueFrom:
                secretKeyRef:
                  name: dev-jarr-app
                  key: jwt-access-secret
          resources:
            requests:
              cpu: 50m
              memory: 64Mi
            limits:
              cpu: 200m
              memory: 256Mi
      containers:
        - name: jarr
          image: gitea.dooplex.hu/admin/jarr:latest