63 lines
3.1 KiB
YAML
63 lines
3.1 KiB
YAML
name: Build and Deploy
|
|
|
|
on:
|
|
push:
|
|
branches:
|
|
- main
|
|
|
|
jobs:
|
|
build-and-push:
|
|
runs-on: ubuntu-latest
|
|
steps:
|
|
- name: Checkout code
|
|
uses: actions/checkout@v3
|
|
|
|
- name: Create Kaniko config file
|
|
run: echo '{"auths":{"${{ secrets.REGISTRY_URL }}":{"username":"${{ secrets.REGISTRY_USER }}","password":"${{ secrets.ACTIONS_PAT }}"}}}' > ${{ gitea.workspace }}/config.json
|
|
|
|
- name: Build and Push Backend
|
|
run: |
|
|
docker run --rm -v ${{ gitea.workspace }}:/workspace -v ${{ gitea.workspace }}/config.json:/kaniko/.docker/config.json gcr.io/kaniko-project/executor:v1.9.0 --context=/workspace --dockerfile=/workspace/Backend/GestionIntegral.Api/Dockerfile --destination=${{ secrets.REGISTRY_URL }}/${{ gitea.actor }}/${{ toLower(gitea.repository_name) }}-backend:latest --destination=${{ secrets.REGISTRY_URL }}/${{ gitea.actor }}/${{ toLower(gitea.repository_name) }}-backend:${{ gitea.sha_short }} --insecure
|
|
|
|
- name: Build and Push Frontend
|
|
run: |
|
|
docker run --rm -v ${{ gitea.workspace }}:/workspace -v ${{ gitea.workspace }}/config.json:/kaniko/.docker/config.json gcr.io/kaniko-project/executor:v1.9.0 --context=/workspace --dockerfile=/workspace/Frontend/Dockerfile --destination=${{ secrets.REGISTRY_URL }}/${{ gitea.actor }}/${{ toLower(gitea.repository_name) }}-frontend:latest --destination=${{ secrets.REGISTRY_URL }}/${{ gitea.actor }}/${{ toLower(gitea.repository_name) }}-frontend:${{ gitea.sha_short }} --insecure
|
|
|
|
deploy:
|
|
runs-on: ubuntu-latest
|
|
needs: build-and-push
|
|
|
|
steps:
|
|
- name: Deploy to Production via SSH
|
|
run: |
|
|
echo "Connecting to production server to deploy..."
|
|
|
|
# 1. Preparar el cliente SSH dentro del contenedor del job
|
|
apt-get update && apt-get install -y openssh-client
|
|
mkdir -p ~/.ssh
|
|
echo "${{ secrets.PROD_SERVER_SSH_KEY }}" > ~/.ssh/id_rsa
|
|
chmod 600 ~/.ssh/id_rsa
|
|
ssh-keyscan -H ${{ secrets.PROD_SERVER_HOST }} >> ~/.ssh/known_hosts
|
|
|
|
# 2. Conectarse al HOST y ejecutar los comandos de despliegue
|
|
ssh ${{ secrets.PROD_SERVER_USER }}@${{ secrets.PROD_SERVER_HOST }} << 'EOF'
|
|
echo "--- CONECTADO AL SERVIDOR DE PRODUCCIÓN ---"
|
|
|
|
# Navegar a la carpeta correcta EN EL HOST
|
|
cd /opt/gestion-integral
|
|
|
|
# Exportar los secretos para que docker-compose los use
|
|
export DB_SA_PASSWORD="${{ secrets.DB_SA_PASSWORD_SECRET }}"
|
|
export JWT_KEY="${{ secrets.JWT_KEY_SECRET }}"
|
|
|
|
# Ejecutar los comandos de Docker en el host, apuntando a sí mismo
|
|
# Usar --password-stdin es más seguro y evita warnings
|
|
echo "${{ secrets.ACTIONS_PAT }}" | docker login 127.0.0.1:5000 -u ${{ secrets.REGISTRY_USER }} --password-stdin
|
|
|
|
# El resto de comandos, ahora sí, funcionarán
|
|
docker compose pull
|
|
docker compose up -d
|
|
docker image prune -af
|
|
|
|
echo "--- ¡¡DESPLIEGUE REALIZADO CON ÉXITO!! ---"
|
|
EOF |