deployment-patterns

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

Updated Mar 18, 2026
One-click install
npx skills add https://github.com/freedom909/real-estate-saas --skill deployment-patterns-freedom909
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: deployment-patterns
Source: https://github.com/freedom909/real-estate-saas/tree/main/.trae/skills/deployment-patterns
Command: npx skills add https://github.com/freedom909/real-estate-saas --skill deployment-patterns-freedom909

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Teams shipping web applications often lack consistent deployment practices, leading to downtime during releases, oversized Docker images, missing health checks, and no tested rollback plan. This Skill provides concrete patterns for deployment strategies, containerization, pipelines, and production readiness. ## Core Features & Use Cases - Deployment Strategies: Guidance on rolling, blue-green, and canary deployments with trade-offs and traffic-splitting diagrams. - Docker & CI/CD Templates: Multi-stage Dockerfiles for Node.js, Go, and Python, plus a GitHub Actions pipeline covering test, build, and deploy stages. - Health Checks & Rollback: Health endpoint implementations, Kubernetes liveness/readiness/startup probes, environment validation with zod, and rollback checklists. - Use Case: Before releasing a new version of a Node.js API, use this Skill to generate a multi-stage Dockerfile, wire up a GitHub Actions pipeline with staging smoke tests, and verify the production readiness checklist. ## Quick Start Ask the AI to set up a CI/CD pipeline and production Dockerfile for your application using the deployment-patterns skill.

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. Run lint, typecheck, and tests on pull requests, then build and push a Docker image to a registry and deploy only on merges to the main branch.

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

Blue-green runs two identical environments and switches 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 before full rollout.

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

Use separate stages for dependency installation, building, and the production runner image. Copy only production node_modules and build output into the final stage, run as a non-root user, and add a HEALTHCHECK instruction.

Does Kubernetes need both liveness and readiness probes?▼

Yes, they serve different purposes. Liveness probes restart unhealthy containers, while readiness probes control whether a pod receives traffic. A startup probe can also protect slow-starting applications from premature liveness failures.

When should I not use a rolling deployment?▼

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