From 35276eab41c3ca80a4ba3b3091fe50192099b4df Mon Sep 17 00:00:00 2001 From: Chaim Date: Mon, 13 Apr 2026 18:33:34 +0000 Subject: [PATCH] Fix CI: use coolify network for job containers Job containers were on isolated network, couldn't reach Coolify API. Now runner config sets container.network=coolify and curl targets http://coolify:8080 (internal container name). Co-Authored-By: Claude Opus 4.6 (1M context) --- .gitea/workflows/deploy.yaml | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) diff --git a/.gitea/workflows/deploy.yaml b/.gitea/workflows/deploy.yaml index e3ada26..3253878 100644 --- a/.gitea/workflows/deploy.yaml +++ b/.gitea/workflows/deploy.yaml @@ -31,7 +31,6 @@ jobs: - name: Trigger Coolify redeploy run: | - # 172.17.0.1 = Docker bridge gateway → host curl -sf \ - "http://172.17.0.1:8000/api/v1/deploy?uuid=my85gabx37ele9aouub8t8ju&force=true" \ + "http://coolify:8080/api/v1/deploy?uuid=my85gabx37ele9aouub8t8ju&force=true" \ -H "Authorization: Bearer ${{ secrets.COOLIFY_TOKEN }}"