From d8643e47fe119c0284c64efd94d0bf8b37e7cc01 Mon Sep 17 00:00:00 2001 From: NANDO9322 Date: Wed, 21 Jan 2026 21:27:01 -0300 Subject: [PATCH] chore: test deploy with host runner --- .forgejo/workflows/deploy.yaml | 18 ++++++------------ 1 file changed, 6 insertions(+), 12 deletions(-) diff --git a/.forgejo/workflows/deploy.yaml b/.forgejo/workflows/deploy.yaml index 427cfc3..c268d17 100644 --- a/.forgejo/workflows/deploy.yaml +++ b/.forgejo/workflows/deploy.yaml @@ -3,34 +3,28 @@ on: push: branches: - dev - - main jobs: build-and-deploy: runs-on: self-hosted - # O PULO DO GATO: Definir container como vazio força o uso do host (Zeus) - container: - image: "" steps: - name: Checkout Code uses: actions/checkout@v4 - - name: Build and Push Image + - name: Build and Push run: | - # Usa o socket do Podman que você já ativou + # Importante: diz ao podman para usar o socket do Zeus export DOCKER_HOST=unix:///run/podman/podman.sock - # Login + # Login no seu registro (garantindo que o Runner tem permissão) echo "${{ secrets.FORGEJO_TOKEN }}" | podman login git.saveinmed.com.br -u ${{ github.actor }} --password-stdin - # Build na pasta backend + # Build e Push usando os binários locais do Zeus podman build -t git.saveinmed.com.br/${{ github.repository }}:latest ./backend - - # Push podman push git.saveinmed.com.br/${{ github.repository }}:latest - - name: Deploy to K3s + - name: Deploy run: | - # Como o kubectl já funciona no Zeus (root), ele vai disparar o deploy + # O kubectl no modo host usará o config do root no Zeus kubectl apply -f k8s/ kubectl rollout restart deployment/photum-backend -n photum