chore: drop the throwaway comment used to force a rebuild

It existed only to make the image content differ so a deploy could be timed. A note about a one-off measurement does not belong in a build file. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01WpTYCBLH58XzrM7n3xPJ5N
chore: note the first myAi deploy with the Watchtower trigger configured
2026-08-24 11:31:23 +00:00 · 2026-08-24 11:25:14 +00:00 · 2026-08-24 11:01:35 +00:00 · 2026-08-24 10:34:16 +00:00
1 changed files with 25 additions and 1 deletions
@@ -108,6 +108,25 @@ jobs:
        run: |
          docker push "${REGISTRY_HOST}/${PAGE_FETCHER_API_IMAGE}:${IMAGE_TAG}"

+      # Watchtower's poll is the fallback, not the mechanism: 30s on staging but 300s on
+      # production, so without this a green run can sit five minutes ahead of the deploy it
+      # claims to have made. Copied from easyDent, including the soft failure -- an unset
+      # secret or an unreachable API must degrade to the poll, never fail the build.
+      - name: Trigger Watchtower redeploy
+        env:
+          URL_STAGING: ${{ secrets.WATCHTOWER_URL_STAGING }}
+          URL_PRODUCTION: ${{ secrets.WATCHTOWER_URL_PRODUCTION }}
+          TOKEN: ${{ secrets.WATCHTOWER_TOKEN }}
+        run: |
+          if [ "${IMAGE_TAG}" = "production" ]; then URL="${URL_PRODUCTION}"; else URL="${URL_STAGING}"; fi
+          if [ -n "${URL}" ] && [ -n "${TOKEN}" ]; then
+            echo "Triggering Watchtower at ${URL}"
+            curl -sf -m 30 -H "Authorization: Bearer ${TOKEN}" "${URL}" && echo "  -> redeploy triggered" \
+              || echo "  -> trigger failed; Watchtower will still pick it up on the next poll"
+          else
+            echo "Watchtower push-trigger not configured (WATCHTOWER_* secrets unset); relying on the poll interval."
+          fi
+
      - name: Reclaim disk space (keep recent build cache)
        if: always()
        run: |
@@ -169,10 +188,15 @@ jobs:
            staging)    HOST=192.168.1.111 ;;
            production) HOST=192.168.1.101 ;;
          esac
+          # `-L` follows redirects and we assert on the FINAL code, because a 302 from `/`
+          # is a healthy answer for a site running in UnderConstruction mode -- it means the
+          # app is up and routing. Asserting a bare 200 failed jecreativ.ro's first
+          # production deploy for doing exactly what it was configured to do.
+          #
          # `|| CODE=000` for the same reason as above: curl exiting non-zero on a
          # connection failure must produce a reportable code, not kill the step before
          # it can say what went wrong. (`-s` without `-f` already tolerates 4xx/5xx.)
-          CODE=$(curl -s -o /dev/null -w '%{http_code}' -m 20 "http://${HOST}:${WEB_PORT}/") || CODE=000
+          CODE=$(curl -sL -o /dev/null -w '%{http_code}' -m 20 "http://${HOST}:${WEB_PORT}/") || CODE=000
          if [ "${CODE}" != "200" ]; then
            echo "::error::Home page returned ${CODE}."
            exit 1
Author	SHA1	Message	Date
claude	bb37314f31	chore: drop the throwaway comment used to force a rebuild Build and Push Docker Images / build (push) Successful in 35s Details Build and Push Docker Images / smoke (push) Successful in 0s Details It existed only to make the image content differ so a deploy could be timed. A note about a one-off measurement does not belong in a build file. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01WpTYCBLH58XzrM7n3xPJ5N	2026-08-24 11:31:23 +00:00
claude	4708b04482	chore: note the first myAi deploy with the Watchtower trigger configured Build and Push Docker Images / build (push) Successful in 38s Details Build and Push Docker Images / smoke (push) Successful in 0s Details Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01WpTYCBLH58XzrM7n3xPJ5N	2026-08-24 11:25:14 +00:00
claude	4e09f27e4d	ci: trigger Watchtower instead of waiting for its poll Build and Push Docker Images / build (push) Successful in 14s Details Build and Push Docker Images / smoke (push) Successful in 0s Details The poll is the fallback, not the mechanism. It is 30s on staging but 300s on production, so a green run could sit five minutes ahead of the deploy it claimed to have made -- the smoke job was absorbing that wait. Copied from easyDent verbatim, including the soft failure: an unset secret or an unreachable API logs and falls back to the poll rather than failing the build. That matters right now because production has no Watchtower HTTP API yet, so the production URL will do nothing until the infra stack there is updated. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01WpTYCBLH58XzrM7n3xPJ5N	2026-08-24 11:01:35 +00:00
claude	449e4d2df3	ci: the deploy health check must follow redirects Build and Push Docker Images / build (push) Successful in 13s Details Build and Push Docker Images / smoke (push) Successful in 15s Details jecreativ.ro's first production deploy went red for behaving exactly as configured: it runs in UnderConstruction mode, so `/` correctly answers 302 to the placeholder, and the check asserted a bare 200. Now `-L` follows the redirect and the FINAL code is asserted. A redirect means the app is up and routing, which is what this step is for; a real failure (502, 500, refused) still reports. The version gate itself was right throughout -- it read 1bafc14 from the production host, including through the under-construction middleware. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01WpTYCBLH58XzrM7n3xPJ5N	2026-08-24 10:34:16 +00:00