Deployment Patterns
Rolling, blue-green, and canary strategies plus CI/CD pipelines, health checks, and production readiness checklists.
- What
- Rolling, blue-green, and canary strategies plus CI/CD pipelines, health checks, and production readiness checklists.
- Cost
- Free
- Needs
- Use "Deployment Patterns" with your Muse.
- Install
- Copy the installer prompt below into your Muse — your agent does the rest.
Curated by Skill Harbor: production deployment workflows and CI/CD best practices for web applications. Walks through the three core rollout strategies with their trade-offs: rolling deployments (zero downtime, but two versions coexist so changes must stay backward compatible), blue-green (instant rollback by switching traffic, at the cost of double infrastructure during cutover), and canary releases, plus the supporting machinery that makes them safe: health checks and readiness probes, environment-specific configuration, Docker containerization, and a production readiness checklist to run before every release. Written to be used at two moments: when setting up a pipeline from scratch, and as a pre-release sanity check when the stakes are high. By @affaan-m, listed here with credit to its creator. From the affaan-m/ECC repository (MIT). Honest caveats: strategy guidance, not a turnkey pipeline; you still adapt it to your platform (Kubernetes, VPS, PaaS) and your team's tolerance for risk. Skill Harbor never reviews the code, review it yourself before use.
Version:
Install
Copy the install package below, then paste it into MuseCommunity-built. Skill Harbor doesn't audit code — review the source before installing.
Use "Deployment Patterns" with your Muse. Prerequisites: the Muse app (mobile or web). Pure guidance skill, nothing to install. A web app you deploy (or plan to). 1. Open the skill: https://github.com/affaan-m/ECC/blob/main/skills/deployment-patterns/SKILL.md and copy the full SKILL.md text. 2. Paste it into a chat with Muse and add: "Help me choose a deployment strategy for [my app]: [stack, hosting, traffic level, tolerance for downtime]." 3. Ask Muse to compare rolling vs blue-green vs canary for your case, then draft the pipeline steps, health checks, and the pre-release readiness checklist. Tip: decide the rollback story before the rollout story. If you cannot describe how you revert in under a minute, the strategy is not finished. Safety: a skill is plain-text instructions; it runs nothing by itself. Review any pipeline config before applying it, never paste secrets into a chat, and review anything Muse proposes before it acts.
Saved to your recent installs. Find it anytime on /connect.
Questions
How do I install a build?
Every product page includes a copy-paste install prompt. Paste it into your Muse and it sets the build up for you — no manual configuration.
Where does my money go?
Straight to the seller. Skill Harbor never processes payments: checkout happens on the seller’s own page, usually Stripe.
What does the ✓ next to a creator’s name mean?
It means we confirmed the identity of the person behind the listing. It says nothing about the code itself — always check a build before installing it.