GitHub Actions Workflow

​

Workflow Overview

​

Deployment Triggers

on:
  push:
    branches: [main]
  schedule:
    - cron: "0 */12 * * *"  # Every 12 hours
  workflow_dispatch:  # Manual trigger

​

Trigger Explanation

1. Push to main - Deploys immediately when code is pushed to the main branch
2. Scheduled - Runs every 12 hours to fetch updated property listings (reduced from hourly to avoid eGO API rate limiting)
3. Manual dispatch - Can be triggered manually from GitHub Actions UI

​

Workflow Steps

​

1. Checkout Code

- name: 🚚 Checkout code
  uses: actions/checkout@v4

​

2. Install Node.js

- name: 🟢 Install Node.js
  uses: actions/setup-node@v4
  with:
    node-version: 20
    cache: "npm"

​

3. Install Dependencies

- name: 📦 Install dependencies
  run: npm ci

​

4. Build Project

- name: 🏗️ Build project
  run: npm run build
  env:
    PUBLIC_EGO_API_TOKEN: ${{ secrets.PUBLIC_EGO_API_TOKEN }}
    EGO_API_BASE_URL: "https://websiteapi.egorealestate.com"

​

5. Validate Build

- name: ✅ Validate build (check properties exist)
  run: |
    if grep -q "property-card" dist/propiedades/index.html 2>/dev/null || grep -q "property-card" dist/es/propiedades/index.html 2>/dev/null; then
      echo "✅ Build válido: propiedades encontradas en el HTML"
    else
      echo "⛔ Build inválido: NO se encontraron propiedades en el HTML generado"
      echo "Abortando deploy para proteger el contenido actual del servidor"
      exit 1
    fi

• Checks if property cards exist in the generated HTML
• Aborts deployment if properties are missing
• Protects against deploying broken builds to production

​

6. Deploy via SFTP

- name: 🚀 Deploy to cdmon via SFTP
  uses: appleboy/[email protected]
  with:
    host: ${{ secrets.SFTP_HOST }}
    username: ${{ secrets.SFTP_USER }}
    password: ${{ secrets.SFTP_PWD }}
    port: 22
    source: "dist/*"
    target: "/web"
    strip_components: 1
    overwrite: true

​

Required GitHub Secrets

​

Adding Secrets

1. Go to GitHub repository Settings → Secrets and variables → Actions
2. Click New repository secret
3. Add each secret with its name and value
4. Secrets are encrypted and not visible after creation

​

Continuous Deployment Strategy

• Automatic updates - Properties are refreshed every 12 hours without manual intervention
• Instant deploys - Code changes on main branch deploy immediately
• Build validation - Prevents broken deployments with automated checks
• Zero-downtime - Files are overwritten atomically via SFTP

​

Benefits

1. Fresh content - Properties are never more than 12 hours out of date
2. No manual work - Developers don’t need to manually deploy
3. Safety checks - Validation prevents deploying incomplete builds
4. Audit trail - All deployments are logged in GitHub Actions

​

Monitoring Deployments

1. Go to the repository’s Actions tab
2. Select the “Deploy to cdmon (SFTP)” workflow
3. View run history, logs, and success/failure status

​

Typical Deployment Time

• Total workflow duration: 2-3 minutes
• Build step: 30-60 seconds
• SFTP upload: 60-90 seconds (depending on file count)

​

Manual Deployment

1. Go to Actions → Deploy to cdmon (SFTP)
2. Click Run workflow
3. Select the main branch
4. Click Run workflow

• Forcing an immediate property update
• Testing deployment after configuration changes
• Recovering from a failed scheduled run

​

Troubleshooting

​

Deployment Failing on Validation

1. Check eGO API status
2. Verify PUBLIC_EGO_API_TOKEN secret is valid
3. Review build logs for API errors

​

SFTP Connection Errors

1. Verify SFTP_HOST, SFTP_USER, and SFTP_PWD secrets
2. Test SFTP connection manually using credentials
3. Check if cdmon hosting is operational

​

Scheduled Runs Not Triggering