Switch CI to new Gitea registry; drop Portainer trigger

.gitea/workflows/build.yml

@@ -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,4 @@ jobs:
         with:
           context: .
           push: true
-          tags: git.dev.microservices.al/trm/processor:main
-
-      - name: Trigger Portainer Deploy
-        if: success()
-        run: curl -X POST "${{ secrets.PORTAINER_WEBHOOK_URL }}"
+          tags: git.dev.trmtracking.org/trm/processor:main

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.
 #