Deployment Procedures
Deployment principles and decision-making for safe production releases.
Learn to THINK, not memorize scripts.
⚠️ How to Use This Skill
This skill teaches deployment principles, not bash scripts to copy.
- Every deployment is unique
- Understand the WHY behind each step
- Adapt procedures to your platform
1. Platform Selection
Decision Tree
What are you deploying?
│
├── Static site / JAMstack
│ └── Vercel, Netlify, Cloudflare Pages
│
├── Simple web app
│ ├── Managed → Railway, Render, Fly.io
│ └── Control → VPS + PM2/Docker
│
├── Microservices
│ └── Container orchestration
│
└── Serverless
└── Edge functions, Lambda
Each Platform Has Different Procedures
| Platform |
Deployment Method |
| Vercel/Netlify |
Git push, auto-deploy |
| Railway/Render |
Git push or CLI |
| VPS + PM2 |
SSH + manual steps |
| Docker |
Image push + orchestration |
| Kubernetes |
kubectl apply |
2. Pre-Deployment Principles
The 4 Verification Categories
| Category |
What to Check |
| Code Quality |
Tests passing, linting clean, reviewed |
| Build |
Production build works, no warnings |
| Environment |
Env vars set, secrets current |
| Safety |
Backup done, rollback plan ready |
Pre-Deployment Checklist
3. Deployment Workflow Principles
The 5-Phase Process
1. PREPARE
└── Verify code, build, env vars
2. BACKUP
└── Save current state before changing
3. DEPLOY
└── Execute with monitoring open
4. VERIFY
└── Health check, logs, key flows
5. CONFIRM or ROLLBACK
└── All good? Confirm. Issues? Rollback.
Phase Principles
| Phase |
Principle |
| Prepare |
Never deploy untested code |
| Backup |
Can't rollback without backup |
| Deploy |
Watch it happen, don't walk away |
| Verify |
Trust but verify |
| Confirm |
Have rollback trigger ready |
4. Post-Deployment Verification
What to Verify
| Check |
Why |
| Health endpoint |
Service is running |
| Error logs |
No new errors |
| Key user flows |
Critical features work |
| Performance |
Response times acceptable |
Verification Window
- First 5 minutes: Active monitoring
- 15 minutes: Confirm stable
- 1 hour: Final verification
- Next day: Review metrics
5. Rollback Principles
When to Rollback
| Symptom |
Action |
| Service down |
Rollback immediately |
| Critical errors |
Rollback |
| Performance >50% degraded |
Consider rollback |
| Minor issues |
Fix forward if quick |
Rollback Strategy by Platform
| Platform |
Rollback Method |
| Vercel/Netlify |
Redeploy previous commit |
| Railway/Render |
Rollback in dashboard |
| VPS + PM2 |
Restore backup, restart |
| Docker |
Previous image tag |
| K8s |
kubectl rollout undo |
Rollback Principles
- Speed over perfection: Rollback first, debug later
- Don't compound errors: One rollback, not multiple changes
- Communicate: Tell team what happened
- Post-mortem: Understand why after stable
6. Zero-Downtime Deployment
Strategies
| Strategy |
How It Works |
| Rolling |
Replace instances one by one |
| Blue-Green |
Switch traffic between environments |
| Canary |
Gradual traffic shift |
Selection Principles
| Scenario |
Strategy |
| Standard release |
Rolling |
| High-risk change |
Blue-green (easy rollback) |
| Need validation |
Canary (test with real traffic) |
7. Emergency Procedures
Service Down Priority
- Assess: What's the symptom?
- Quick fix: Restart if unclear
- Rollback: If restart doesn't help
- Investigate: After stable
Investigation Order
| Check |
Common Issues |
| Logs |
Errors, exceptions |
| Resources |
Disk full, memory |
| Network |
DNS, firewall |
| Dependencies |
Database, APIs |
8. Anti-Patterns
| ❌ Don't |
✅ Do |
| Deploy on Friday |
Deploy early in week |
| Rush deployment |
Follow the process |
| Skip staging |
Always test first |
| Deploy without backup |
Backup before deploy |
| Walk away after deploy |
Monitor for 15+ min |
| Multiple changes at once |
One change at a time |
9. Decision Checklist
Before deploying:
10. Best Practices
- Small, frequent deploys over big releases
- Feature flags for risky changes
- Automate repetitive steps
- Document every deployment
- Review what went wrong after issues
- Test rollback before you need it
Remember: Every deployment is a risk. Minimize risk through preparation, not speed.
When to Use
This skill is applicable to execute the workflow or actions described in the overview.
1---2name: deployment-procedures3description: "Production deployment principles and decision-making. Safe deployment workflows, rollback strategies, and verification. Teaches thinking, not scripts."4allowed-tools: Read, Glob, Grep, Bash5risk: unknown6source: community7metadata:8 source: https://skillmd.com/skills/mayurrathi/deployment-procedures9---1011# Deployment Procedures1213> Deployment principles and decision-making for safe production releases.14> **Learn to THINK, not memorize scripts.**1516---1718## ⚠️ How to Use This Skill1920This skill teaches **deployment principles**, not bash scripts to copy.2122- Every deployment is unique23- Understand the WHY behind each step24- Adapt procedures to your platform2526---2728## 1. Platform Selection2930### Decision Tree3132```33What are you deploying?34│35├── Static site / JAMstack36│ └── Vercel, Netlify, Cloudflare Pages37│38├── Simple web app39│ ├── Managed → Railway, Render, Fly.io40│ └── Control → VPS + PM2/Docker41│42├── Microservices43│ └── Container orchestration44│45└── Serverless46 └── Edge functions, Lambda47```4849### Each Platform Has Different Procedures5051| Platform | Deployment Method |52|----------|------------------|53| **Vercel/Netlify** | Git push, auto-deploy |54| **Railway/Render** | Git push or CLI |55| **VPS + PM2** | SSH + manual steps |56| **Docker** | Image push + orchestration |57| **Kubernetes** | kubectl apply |5859---6061## 2. Pre-Deployment Principles6263### The 4 Verification Categories6465| Category | What to Check |66|----------|--------------|67| **Code Quality** | Tests passing, linting clean, reviewed |68| **Build** | Production build works, no warnings |69| **Environment** | Env vars set, secrets current |70| **Safety** | Backup done, rollback plan ready |7172### Pre-Deployment Checklist7374- [ ] All tests passing75- [ ] Code reviewed and approved76- [ ] Production build successful77- [ ] Environment variables verified78- [ ] Database migrations ready (if any)79- [ ] Rollback plan documented80- [ ] Team notified81- [ ] Monitoring ready8283---8485## 3. Deployment Workflow Principles8687### The 5-Phase Process8889```901. PREPARE91 └── Verify code, build, env vars92932. BACKUP94 └── Save current state before changing95963. DEPLOY97 └── Execute with monitoring open98994. VERIFY100 └── Health check, logs, key flows1011025. CONFIRM or ROLLBACK103 └── All good? Confirm. Issues? Rollback.104```105106### Phase Principles107108| Phase | Principle |109|-------|-----------|110| **Prepare** | Never deploy untested code |111| **Backup** | Can't rollback without backup |112| **Deploy** | Watch it happen, don't walk away |113| **Verify** | Trust but verify |114| **Confirm** | Have rollback trigger ready |115116---117118## 4. Post-Deployment Verification119120### What to Verify121122| Check | Why |123|-------|-----|124| **Health endpoint** | Service is running |125| **Error logs** | No new errors |126| **Key user flows** | Critical features work |127| **Performance** | Response times acceptable |128129### Verification Window130131- **First 5 minutes**: Active monitoring132- **15 minutes**: Confirm stable133- **1 hour**: Final verification134- **Next day**: Review metrics135136---137138## 5. Rollback Principles139140### When to Rollback141142| Symptom | Action |143|---------|--------|144| Service down | Rollback immediately |145| Critical errors | Rollback |146| Performance >50% degraded | Consider rollback |147| Minor issues | Fix forward if quick |148149### Rollback Strategy by Platform150151| Platform | Rollback Method |152|----------|----------------|153| **Vercel/Netlify** | Redeploy previous commit |154| **Railway/Render** | Rollback in dashboard |155| **VPS + PM2** | Restore backup, restart |156| **Docker** | Previous image tag |157| **K8s** | kubectl rollout undo |158159### Rollback Principles1601611. **Speed over perfection**: Rollback first, debug later1622. **Don't compound errors**: One rollback, not multiple changes1633. **Communicate**: Tell team what happened1644. **Post-mortem**: Understand why after stable165166---167168## 6. Zero-Downtime Deployment169170### Strategies171172| Strategy | How It Works |173|----------|--------------|174| **Rolling** | Replace instances one by one |175| **Blue-Green** | Switch traffic between environments |176| **Canary** | Gradual traffic shift |177178### Selection Principles179180| Scenario | Strategy |181|----------|----------|182| Standard release | Rolling |183| High-risk change | Blue-green (easy rollback) |184| Need validation | Canary (test with real traffic) |185186---187188## 7. Emergency Procedures189190### Service Down Priority1911921. **Assess**: What's the symptom?1932. **Quick fix**: Restart if unclear1943. **Rollback**: If restart doesn't help1954. **Investigate**: After stable196197### Investigation Order198199| Check | Common Issues |200|-------|--------------|201| **Logs** | Errors, exceptions |202| **Resources** | Disk full, memory |203| **Network** | DNS, firewall |204| **Dependencies** | Database, APIs |205206---207208## 8. Anti-Patterns209210| ❌ Don't | ✅ Do |211|----------|-------|212| Deploy on Friday | Deploy early in week |213| Rush deployment | Follow the process |214| Skip staging | Always test first |215| Deploy without backup | Backup before deploy |216| Walk away after deploy | Monitor for 15+ min |217| Multiple changes at once | One change at a time |218219---220221## 9. Decision Checklist222223Before deploying:224225- [ ] **Platform-appropriate procedure?**226- [ ] **Backup strategy ready?**227- [ ] **Rollback plan documented?**228- [ ] **Monitoring configured?**229- [ ] **Team notified?**230- [ ] **Time to monitor after?**231232---233234## 10. Best Practices2352361. **Small, frequent deploys** over big releases2372. **Feature flags** for risky changes2383. **Automate** repetitive steps2394. **Document** every deployment2405. **Review** what went wrong after issues2416. **Test rollback** before you need it242243---244245> **Remember:** Every deployment is a risk. Minimize risk through preparation, not speed.246247## When to Use248This skill is applicable to execute the workflow or actions described in the overview.