rede5/gohorsejobs
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

ajustes novos

Browse source
This commit is contained in:
Marcus 2026-01-31 15:43:06 -03:00
parent f5d58d0c91
commit fc8034ed4e
1 changed files with 6 additions and 7 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

13
.forgejo/workflows/deploy.yaml
View file

@ -9,9 +9,12 @@ env:
REGISTRY: pipe.gohorsejobs.com REGISTRY: pipe.gohorsejobs.com
IMAGE_NAMESPACE: bohessefm IMAGE_NAMESPACE: bohessefm
DOCKER_HOST: unix:///run/docker.sock DOCKER_HOST: unix:///run/docker.sock
# ATIVA O BUILDKIT: Necessário para usar --mount (cache) no Dockerfile
DOCKER_BUILDKIT: 1
jobs: jobs:
build-and-push: build-and-push:
# Ajustado para usar as labels que aparecem no seu Runner ID 50
runs-on: [self-hosted, linux-amd64] runs-on: [self-hosted, linux-amd64]
defaults: defaults:
run: run:
@ -28,17 +31,16 @@ jobs:
- name: Build & Push Backend - name: Build & Push Backend
run: | run: |
# Usamos --quiet no push para não inundar o Forgejo com logs de progresso (evita Erro 500) # Build usando BuildKit (suporta o cache do seu Dockerfile)
docker build -t ${{ env.REGISTRY }}/${{ env.IMAGE_NAMESPACE }}/gohorsejobs:${{ github.sha }} \ docker build -t ${{ env.REGISTRY }}/${{ env.IMAGE_NAMESPACE }}/gohorsejobs:${{ github.sha }} \
-t ${{ env.REGISTRY }}/${{ env.IMAGE_NAMESPACE }}/gohorsejobs:latest ./backend -t ${{ env.REGISTRY }}/${{ env.IMAGE_NAMESPACE }}/gohorsejobs:latest ./backend
# Push --quiet evita o flood de logs que derruba o Forgejo
docker push --quiet ${{ env.REGISTRY }}/${{ env.IMAGE_NAMESPACE }}/gohorsejobs:${{ github.sha }} docker push --quiet ${{ env.REGISTRY }}/${{ env.IMAGE_NAMESPACE }}/gohorsejobs:${{ github.sha }}
docker push --quiet ${{ env.REGISTRY }}/${{ env.IMAGE_NAMESPACE }}/gohorsejobs:latest docker push --quiet ${{ env.REGISTRY }}/${{ env.IMAGE_NAMESPACE }}/gohorsejobs:latest
- name: Build & Push Backoffice - name: Build & Push Backoffice
run: | run: |
# O build do Backoffice (NestJS) é o que mais trava.
# Reduzimos o log e focamos no push silencioso.
docker build -t ${{ env.REGISTRY }}/${{ env.IMAGE_NAMESPACE }}/backoffice:${{ github.sha }} \ docker build -t ${{ env.REGISTRY }}/${{ env.IMAGE_NAMESPACE }}/backoffice:${{ github.sha }} \
-t ${{ env.REGISTRY }}/${{ env.IMAGE_NAMESPACE }}/backoffice:latest ./backoffice -t ${{ env.REGISTRY }}/${{ env.IMAGE_NAMESPACE }}/backoffice:latest ./backoffice
@ -50,7 +52,6 @@ jobs:
runs-on: [self-hosted, linux-amd64] runs-on: [self-hosted, linux-amd64]
steps: steps:
- name: Install Deploy Tools - name: Install Deploy Tools
# Removido nodejs daqui (não parece necessário para rodar kubectl)
run: apk add --no-cache curl kubectl run: apk add --no-cache curl kubectl
- name: Checkout code - name: Checkout code
@ -61,12 +62,10 @@ jobs:
kubectl create namespace gohorsejobsdev --dry-run=client -o yaml | kubectl apply -f - kubectl create namespace gohorsejobsdev --dry-run=client -o yaml | kubectl apply -f -
kubectl apply -f k8s/dev/ -n gohorsejobsdev kubectl apply -f k8s/dev/ -n gohorsejobsdev
# Rollout progressivo: garante que o K8s não derrube tudo de uma vez
kubectl -n gohorsejobsdev set image deployment/gohorse-backend-dev \ kubectl -n gohorsejobsdev set image deployment/gohorse-backend-dev \
backend=${{ env.REGISTRY }}/${{ env.IMAGE_NAMESPACE }}/gohorsejobs:${{ github.sha }} backend=${{ env.REGISTRY }}/${{ env.IMAGE_NAMESPACE }}/gohorsejobs:${{ github.sha }}
kubectl -n gohorsejobsdev set image deployment/gohorse-backoffice-dev \ kubectl -n gohorsejobsdev set image deployment/gohorse-backoffice-dev \
backoffice=${{ env.REGISTRY }}/${{ env.IMAGE_NAMESPACE }}/backoffice:${{ github.sha }} backoffice=${{ env.REGISTRY }}/${{ env.IMAGE_NAMESPACE }}/backoffice:${{ github.sha }}
# Verifica se o deploy deu certo (se travar aqui, o problema é no K3s, não no Forgejo) kubectl -n gohorsejobsdev rollout status deployment/gohorse-backend-dev --timeout=120s
kubectl -n gohorsejobsdev rollout status deployment/gohorse-backend-dev --timeout=90s