Trigger Komodo Stack redeploy on successful build

.gitea/workflows/build.yml

@@ -2,7 +2,7 @@ name: Build and Push processor
 
 on:
   push:
-    branches: [main]
+    branches: [dev]
     paths:
       - 'src/**'
       - 'test/**'
@@ -52,7 +52,7 @@ jobs:
       - name: Login to Gitea Registry
         uses: docker/login-action@v3
         with:
-          registry: git.dev.microservices.al
+          registry: git.dev.trmtracking.org
           username: ${{ secrets.REGISTRY_USERNAME }}
           password: ${{ secrets.REGISTRY_PASSWORD }}
 
@@ -61,8 +61,18 @@ jobs:
         with:
           context: .
           push: true
-          tags: git.dev.microservices.al/trm/processor:main
+          tags: git.dev.trmtracking.org/trm/processor:dev
 
-      - name: Trigger Portainer Deploy
+      - name: Trigger Komodo Stack redeploy
         if: success()
-        run: curl -X POST "${{ secrets.PORTAINER_WEBHOOK_URL }}"
+        env:
+          URL: ${{ secrets.KOMODO_STACK_WEBHOOK_URL }}
+          SECRET: ${{ secrets.KOMODO_WEBHOOK_SECRET }}
+        run: |
+          body='{"ref":"refs/heads/dev"}'
+          sig=$(printf '%s' "$body" | openssl dgst -sha256 -hmac "$SECRET" | awk '{print $2}')
+          curl -fsS -X POST \
+            -H 'Content-Type: application/json' \
+            -H "X-Hub-Signature-256: sha256=$sig" \
+            -d "$body" \
+            "$URL"

compose.dev.yaml

@@ -5,7 +5,7 @@
 # day-to-day development, run `pnpm dev` directly against host-exposed services.
 #
 # For STAGE and PRODUCTION deployment, use the multi-service compose in
-# the sibling `deploy/` repo (https://git.dev.microservices.al/trm/deploy),
+# the sibling `deploy/` repo (https://git.dev.trmtracking.org/trm/deploy),
 # which references this service by its registry image tag instead of
 # building locally.
 #