Automating CI/CD Pipelines with Docker, GitHub Actions, and Linux Servers

From Manual Deployments to Deterministic Automation

Manual SSH commands and manual file uploads are the leading cause of production outages, configuration drift, and security vulnerabilities. A modern engineering pipeline demands automated verification, containerized builds, and zero-downtime deployment strategies.

1. Multi-Stage Docker Builds

Creating lean, secure production containers requires multi-stage builds that keep compilers, package managers, and development source files out of the final runtime image:

# Multi-stage production build example
FROM node:20-alpine AS builder
WORKDIR /app
COPY package*.json ./
RUN npm ci
COPY . .
RUN npm run build

FROM node:20-alpine AS runner
WORKDIR /app
ENV NODE_ENV=production
COPY --from=builder /app/dist ./dist
COPY --from=builder /app/package*.json ./
RUN npm ci --only=production && npm cache clean --force
USER node
EXPOSE 3000
CMD ["node", "dist/server.js"]

2. Automated GitHub Actions Pipeline

Every pull request must trigger automated linting, unit tests, security audits, and container building before merging to the main production branch. Utilizing GitHub Actions and self-hosted runners enables fast build caches and reliable verification.

3. Blue-Green and Rolling Deployments

To deploy without dropping active user connections, rolling updates or blue-green switches ensure that the new container is healthy and responding to HTTP health checks before the reverse proxy (Nginx or Apache) redirects traffic from the older instance.