Freelance Web Development, Github, Uncategorized, Web Development Basics

The DevOps Journey: Automating Deployment Pipelines with GitHub Actions

Posted by

On March 14, 2025

The server crashed during peak trading hours, and I still have nightmares about it.

Our e-commerce platform had just gone viral, but our deployment process was stuck in 2010: a tangled mess of manual SSH commands, inconsistent environments, and a deployment checklist longer than Tolstoy’s War and Peace. Then came Black Friday. A last-minute “hotfix” deployed via SFTP brought the entire site down—costing $14,000 per minute in lost revenue.

The next morning, I declared war on manual deployments.

The Dark Ages: Manual Deployments

Our old process looked like this:

Commit code → 2. Run tests locally → 3. Pray → 4. Zip files → 5. SSH into prod → 6. Apologize to users.

The team dreaded Thursdays (“deployment day”). We’d huddle around a single terminal, copy-pasting commands from a Google Doc, while someone nervously narrated: “Wait, did you remember to restart NGINX?”

Enter GitHub Actions: Our CI/CD Lifeline

I stumbled on GitHub Actions while debugging a git merge disaster. The concept was irresistible: automate everything. No more “works on my machine” excuses. No more human error.

We started with a simple goal: automate testing on every pull request.

The First Workflow: .github/workflows/test.yml

				
					name: Run Tests  
on: [pull_request]  

jobs:  
  test:  
    runs-on: ubuntu-latest  
    steps:  
      - name: Checkout code  
        uses: actions/checkout@v4  
      - name: Install Node.js  
        uses: actions/setup-node@v4  
        with:  
          node-version: '20.x'  
      - name: Install dependencies  
        run: npm ci  
      - name: Run tests  
        run: npm test

This YAML file became our safety net. Suddenly:

Broken tests blocked PR merges.
New hires could contribute without “breaking prod.”
We stopped arguing about whose code “should’ve worked.”

Leveling Up: From Tests to Deployment

Emboldened, we automated deployments using environment-specific workflows

Staging on Push to main:

				
					deploy-staging:  
    needs: test  
    runs-on: ubuntu-latest  
    environment: staging  
    steps:  
      - uses: actions/checkout@v4  
      - run: npm run build  
      - uses: azure/webapps-deploy@v2  
        with:  
          app-name: "staging-app"  
          publish-profile: ${{ secrets.AZURE_STAGING_PUBLISH_PROFILE }}

Production on Tag Release:

				
					deploy-prod:  
    needs: deploy-staging  
    if: startsWith(github.ref, 'refs/tags/v')  
    environment: production  
    runs-on: ubuntu-latest  
    steps:  
      - uses: actions/checkout@v4  
      - run: npm run build  
      - uses: azure/webapps-deploy@v2  
        with:  
          app-name: "prod-app"  
          publish-profile: ${{ secrets.AZURE_PROD_PUBLISH_PROFILE }}

The Game-Changers

1. Seamless Rollbacks

When a bug slipped into prod, we re-ran the previous tag’s workflow. No more frantic git reflog archaeology.

2. Dockerized Consistency

Adding a container step eliminated “works locally, breaks on server” chaos:

				
					- name: Build and Push Docker Image  
  uses: docker/build-push-action@v5  
  with:  
    tags: "myapp:${{ github.sha }}"  
    push: true

3. Slack Notifications for Peace of Mind

				
					- name: Notify Slack  
  uses: slackapi/slack-github-action@v1  
  with:  
    channel-id: 'deployments'  
    slack-message: "✅ Deployment to ${{ github.event.inputs.environment }} succeeded!"

The Pitfalls We Survived

Secret Management: Accidentally committing .env files to logs (now encrypted with actions/github-script).
Concurrency Issues: Two deployments clashing until we added concurrency: production groups.
Cost Surprises: A runaway workflow loop once burned $50 in Azure credits. (RIP, budget.)

The Results

Deployment time dropped from 45 minutes to 7.
Zero post-deploy outages in 6 months.
Friday afternoons became “innovation hours” instead of “recovery marathons.”

Why This Matters for Small Teams

You don’t need a dedicated DevOps engineer to:

Enforce consistency with containerization.
Scale confidently using parallel jobs.
Sleep better with automated rollbacks.

Start Your Automation Today

Steal our template: Fork GitHub Actions Starter Workflows.
Experiment in a branch: Use workflow_dispatch for manual triggers.
Celebrate: The first time a workflow deploys while you sip coffee, you’ll feel like a wizard.

Blog