deployment

Configure web servers, CI/CD pipelines, Docker, and zero-downtime deployment strategies for frontend applications.

2|Updated Jun 8, 2026
One-click install
npx skills add https://github.com/lunaticwithaduck/easytech3d --skill deployment-lunaticwithaduck
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: deployment
Source: https://github.com/lunaticwithaduck/easytech3d/tree/main/.claude/skills/deployment
Command: npx skills add https://github.com/lunaticwithaduck/easytech3d --skill deployment-lunaticwithaduck

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Setting up production frontend infrastructure requires juggling nginx or Caddy configs, CI/CD pipelines, Docker images, hosting platforms, and zero-downtime strategies, and small mistakes like missing try_files rules or wrong cache headers cause broken routes and stale assets. ## Core Features & Use Cases - Web Server Configuration: Production-ready nginx and Caddy configs covering SPA routing, reverse proxies, SSL/TLS with Let's Encrypt, gzip/Brotli compression, rate limiting, and split cache headers. - CI/CD Pipelines: Complete GitHub Actions and GitLab CI workflows with lint, test, build, Docker push, environment protection, PR previews, and Slack notifications. - Docker & Zero-Downtime Deployment: Multi-stage Dockerfiles, Docker Compose production setups, PM2 process management, and blue-green deployment scripts with health checks and instant rollback. - Use Case: You need to deploy a React SPA to a VPS. Use this Skill to generate an nginx config with SPA fallback and immutable asset caching, a GitHub Actions pipeline that builds and pushes a Docker image, and a blue-green deploy script that switches traffic only after health checks pass. ## Quick Start Ask the assistant to generate a production nginx configuration and GitHub Actions pipeline for deploying your SPA with zero-downtime blue-green releases.

Frequently Asked Questions about deployment

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

FAQPage Schema
How do I configure nginx for SPA routing?▼

Add try_files $uri $uri/ /index.html inside the root location block so unknown paths fall back to index.html. Serve hashed static assets with immutable one-year cache headers and keep HTML responses set to no-cache so browsers always fetch the latest asset references.

nginx vs Caddy for serving a frontend app?▼

Caddy provides automatic HTTPS via Let's Encrypt, built-in HTTP/3, and a simpler Caddyfile syntax, making it ideal for quick setups. nginx offers finer-grained control, built-in rate limiting, and higher throughput for high-traffic or complex routing scenarios.

How do I set up a GitHub Actions deployment pipeline?▼

Create jobs for lint, test, and build that run in sequence, then add a Docker job that builds and pushes to GHCR using docker/build-push-action with GHA layer caching. Deploy via SSH with appleboy/ssh-action, protect the production environment with required reviewers, and verify with a health check curl.

How do I achieve zero-downtime deployment with Docker?▼

Use a blue-green strategy with two service instances on different ports behind an nginx upstream. Deploy to the standby slot, poll its health endpoint until ready, switch the nginx symlink config and reload, then stop the old instance for instant rollback capability.

Why do users see stale assets after deploying a new build?▼

This happens when index.html is cached as immutable, so browsers never fetch updated asset references. Set Cache-Control no-cache on HTML files and reserve immutable one-year caching only for content-hashed filenames like app.a1b2c3d.js.

Does GitHub Pages support SPA routing natively?▼

No, GitHub Pages lacks server-side routing, so direct URL access returns 404. The standard workaround uses a custom 404.html that redirects to index.html with the path encoded in a query string, which the app then restores via history.replaceState.