deployment-patterns

Implements CI/CD pipelines, Docker builds, health checks, and rollback strategies for web application deployments.

Updated Mar 25, 2026
One-click install
npx skills add https://github.com/Femad-6/my-skills --skill deployment-patterns-femad-6
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: deployment-patterns
Source: https://github.com/Femad-6/my-skills/tree/main/.github/skills/deployment-patterns
Command: npx skills add https://github.com/Femad-6/my-skills --skill deployment-patterns-femad-6

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Shipping web applications to production involves many failure-prone decisions: choosing a deployment strategy, writing efficient Dockerfiles, wiring CI/CD pipelines, and verifying readiness. This Skill provides concrete, copy-ready patterns for each of these steps so teams avoid common production mistakes. ## Core Features & Use Cases - Deployment Strategies: Guidance and trade-offs for rolling, blue-green, and canary deployments with diagrams of traffic flow. - Docker & CI/CD Templates: Multi-stage Dockerfiles for Node.js, Go, and Python/Django, plus a GitHub Actions pipeline covering test, build, and deploy stages. - Production Readiness: Health check endpoint patterns, Kubernetes liveness/readiness/startup probes, environment validation with zod, rollback procedures, and a full pre-release checklist. - Use Case: When containerizing a Django app and setting up its first production pipeline, use this Skill to generate a multi-stage Dockerfile, a GitHub Actions workflow, and a readiness checklist in one pass. ## Quick Start Ask the assistant to create a production Dockerfile and GitHub Actions CI/CD pipeline with health checks and a rollback plan for your application.

Frequently Asked Questions about deployment-patterns

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I set up a CI/CD pipeline with GitHub Actions?

Define sequential jobs for test, build, and deploy in a workflow YAML file triggered on pushes to main. The test job runs lint, typecheck, and tests; the build job pushes a Docker image to a registry; the deploy job releases to production using the commit SHA as the image tag.

What is the difference between blue-green and canary deployment?

Blue-green runs two identical environments and switches all traffic atomically, enabling instant rollback but requiring double infrastructure. Canary routes a small traffic percentage to the new version first, catching issues with real traffic but requiring traffic-splitting and monitoring infrastructure.

How do I write a multi-stage Dockerfile for Node.js?

Use separate stages for dependency installation, building, and the production runtime based on node:22-alpine. Copy only production node_modules and build output into the final stage, run as a non-root user, and add a HEALTHCHECK instruction hitting the /health endpoint.

What Kubernetes probes should a web application configure?

Configure three probes against the /health endpoint: a livenessProbe to restart unhealthy containers, a readinessProbe to control traffic routing, and a startupProbe with a high failureThreshold to allow slow application startup without premature restarts.

When should I avoid a rolling deployment strategy?

Avoid rolling deployments when changes are not backward-compatible, since old and new versions run simultaneously during rollout. Use blue-green for critical services needing instant rollback, or canary for risky changes on high-traffic services.