name: release - build & deploy naar productie # Draait wanneer je in Forgejo een release publiceert. # De release-tag (bv. v1.2.0) wordt de image-tag op productie. on: release: types: [published] concurrency: group: deploy-prod cancel-in-progress: false jobs: build-and-deploy: runs-on: prod # jouw prod-runner (productieserver) env: REGISTRY: ${{ vars.REGISTRY }} IMAGE_NAME: ${{ github.repository }} # bes-r/teach steps: - uses: actions/checkout@v4 - name: Image-tags bepalen id: meta run: | IMAGE="${REGISTRY}/${IMAGE_NAME}" VERSION="${GITHUB_REF_NAME}" # de release-/tagnaam, bv. v1.2.0 echo "image=${IMAGE}" >> "$GITHUB_OUTPUT" echo "version_tag=${IMAGE}:${VERSION}" >> "$GITHUB_OUTPUT" echo "latest_tag=${IMAGE}:latest" >> "$GITHUB_OUTPUT" echo "version=${VERSION}" >> "$GITHUB_OUTPUT" # Platte docker build/push (HTTP-registry, zie README voor insecure-registry). - name: Login, build & push run: | echo "${{ secrets.REGISTRY_TOKEN }}" | docker login "$REGISTRY" -u "${{ secrets.REGISTRY_USER }}" --password-stdin docker build \ --build-arg APP_VERSION="${{ steps.meta.outputs.version }}" \ -t "${{ steps.meta.outputs.version_tag }}" \ -t "${{ steps.meta.outputs.latest_tag }}" . docker push "${{ steps.meta.outputs.version_tag }}" docker push "${{ steps.meta.outputs.latest_tag }}" # Deploy via gewone ssh (geen externe action nodig). - name: Deploy naar productie-VM run: | echo "${{ secrets.PROD_SSH_KEY }}" > deploy_key chmod 600 deploy_key ssh -o StrictHostKeyChecking=no -o UserKnownHostsFile=/dev/null -o BatchMode=yes -o ConnectTimeout=15 \ -i deploy_key ${{ secrets.PROD_USER }}@${{ secrets.PROD_HOST }} \ "set -e && cd ${{ secrets.PROD_DEPLOY_PATH }} && echo '${{ secrets.REGISTRY_TOKEN }}' | docker login ${{ vars.REGISTRY }} -u '${{ secrets.REGISTRY_USER }}' --password-stdin && sed -i 's|^IMAGE=.*|IMAGE=${{ steps.meta.outputs.version_tag }}|' .env && docker compose -f compose.deploy.yaml pull app && docker compose -f compose.deploy.yaml up -d && docker image prune -f" rm -f deploy_key