CI/CD Setup for Websites via GitHub Actions

CI/CD Setup for Websites via GitHub Actions

Every second production release fails due to human error: a file wasn't uploaded, a config wasn't updated, tests were skipped. CI/CD eliminates these risks. With 5+ years of experience, we've set up over 50 pipelines for projects ranging from landing pages to high-load SaaS. GitHub Actions is our go-to for fast automation. Order a setup and get a ready pipeline in 1–5 days.

Why GitHub Actions?

Unlike Jenkins or GitLab CI, there's no need to spin up a separate server, configure webhooks, or install plugins. Everything is managed via YAML files in the repository. For public projects, it's free indefinitely. For private ones, you get 2000 minutes per month on the free tier—enough for 400–1000 deploys. If you exceed that, attach a self-hosted runner on your server—minutes are not consumed. GitHub Actions is 2x faster to set up than GitLab CI and requires no server unlike Jenkins.

How to Speed Up Builds with Caching

Dependency caching is the main accelerator. actions/setup-node with cache: 'npm' automatically caches ~/.npm. For PHP, use actions/cache with a key based on composer.lock. Example for Composer:

- uses: actions/cache@v4 with: path: vendor key: composer-${{ hashFiles('composer.lock') }} 

After cache warm-up, run time drops from 3–5 minutes to 60–90 seconds. Matrix builds (multiple Node.js versions) run in parallel and are cached separately. The team saves 3 hours per week, which at average DevOps rates amounts to up to $350 per month.

Workflow Structure

A minimal workflow for a Node.js site with SSH deployment:

---
name: Deploy
on:
  push:
    branches: [main]
jobs:
  test:
    runs-on: ubuntu-22.04
    steps:
      - uses: actions/checkout@v4
      - uses: actions/setup-node@v4
        with:
          node-version: '20'
          cache: 'npm'
      - run: npm ci
      - run: npm test
  build:
    needs: test
    runs-on: ubuntu-22.04
    steps:
      - uses: actions/checkout@v4
      - uses: actions/setup-node@v4
        with:
          node-version: '20'
          cache: 'npm'
      - run: npm ci
      - run: npm run build
      - uses: actions/upload-artifact@v4
        with:
          name: dist
          path: dist/
  deploy:
    needs: build
    runs-on: ubuntu-22.04
    environment: production
    steps:
      - uses: actions/download-artifact@v4
        with:
          name: dist
          path: dist/
      - name: Deploy via rsync
        uses: burnett01/[email protected]
        with:
          switches: -avzr --delete
          path: dist/
          remote_path: /var/www/mysite
          remote_host: ${{ secrets.DEPLOY_HOST }}
          remote_user: deploy
          remote_key: ${{ secrets.DEPLOY_KEY }}

Three jobs: test, build, deploy. If tests fail, build doesn't run. We use artifacts to pass built files.

Secret Management

All sensitive data goes into Settings → Secrets and variables → Actions. No keys or passwords end up in code. For different environments, use Environments—each set of secrets is isolated. Production deployment can be protected by manual approval.

- name: Configure .env
  run: |
    echo "DATABASE_URL=${{ secrets.DATABASE_URL }}" >> .env
    echo "APP_KEY=${{ secrets.APP_KEY }}" >> .env

Docker Build and Registry Push

If deployment uses containers:

---
- name: Build and push Docker image
  uses: docker/build-push-action@v5
  with:
    context: .
    push: true
    tags: ghcr.io/${{ github.repository }}:${{ github.sha }}
    cache-from: type=gha
    cache-to: type=gha,mode=max

GitHub Container Registry is free, authentication via built-in GITHUB_TOKEN.

Status Notifications

---
- name: Notify Telegram on failure
  if: failure()
  uses: appleboy/telegram-action@master
  with:
    to: ${{ secrets.TELEGRAM_CHAT_ID }}
    token: ${{ secrets.TELEGRAM_TOKEN }}
    message: "❌ Deploy failed: ${{ github.repository }} @ ${{ github.sha }}"

if: failure() runs only on failure. For start and success notifications, use if: always().

Step-by-Step CI/CD Setup Guide

1. Create a .github/workflows directory in the repo root.
2. Add a deploy.yml file with the configuration (example above).
3. Set up secrets in Settings → Secrets and variables → Actions.
4. Push changes to the main branch—the workflow triggers automatically.
5. Check the status in the Actions tab of the repository.
6. On success, deployment is done. On failure, you'll get a notification.

Comparison: GitHub Actions vs Other CI/CD

GitHub Actions is easier to set up than Jenkins and requires no dedicated server. For most web projects, it's the optimal choice.

Setup Stages and Timeline

What's Included

We provide the full CI/CD setup cycle:

• Analysis of the current deployment process and project architecture
• Creation of a YAML workflow with tests, build, and deployment
• Configuration of secrets and environments in the repository
• Build speed optimization (caching, matrices)
• Integration of notifications (Telegram, Slack, email)
• Workflow documentation and team instructions
• Training developers on pipeline usage

---
name: Deploy
on: [push]
jobs:
  test:
    runs-on: ubuntu-22.04
    steps:
      - uses: actions/checkout@v4
      - uses: actions/setup-node@v4
        with:
          node-version: '20'
          cache: 'npm'
      - run: npm ci
      - run: npm test
  build:
    needs: test
    runs-on: ubuntu-22.04
    steps:
      - uses: actions/checkout@v4
      - uses: actions/setup-node@v4
        with:
          node-version: '20'
          cache: 'npm'
      - run: npm ci
      - run: npm run build
      - name: Build Docker image
        run: docker build -t myapp .
      - name: Push to registry
        run: docker push ghcr.io/myorg/myapp:latest
  deploy:
    needs: build
    runs-on: ubuntu-22.04
    steps:
      - name: Deploy via SSH
        uses: appleboy/[email protected]
        with:
          host: ${{ secrets.DEPLOY_HOST }}
          username: deploy
          key: ${{ secrets.DEPLOY_KEY }}
          script: |
            docker pull ghcr.io/myorg/myapp:latest
            docker-compose up -d

Our Results and Experience

For 5+ years, we've set up CI/CD for projects of varying complexity—from landing pages to high-load SaaS. Over 50 implemented pipelines with guaranteed stable operation. Each case is documented so the client's team can maintain and extend the pipeline independently. Downtime costs due to deployment errors can reach $1,400 per day—CI/CD eliminates that.

Timeline and Pricing

• Basic workflow (test + SSH deploy) — 1–2 days
• Full pipeline (matrices, Docker, notifications, manual approvals) — 3–5 days

Cost is calculated individually based on complexity and stack. Contact us for a consultation—we'll find the optimal solution for your project.