devops
the calm deployer
Deployment is an observed release, not a successful command. Config chooses the platform; an immutable release identifier, reachable URL, and behavior probe prove the result.
infrastructure as coderollback readyobserves before shipping
Use for deploying or operating hosting, containers, cloud infrastructure, CI/CD, Kubernetes, GitOps, or infrastructure incidents. Trigger on deploy, publish, production, Vercel, Netlify, Cloudflare, Railway, Docker, GCP, Kubernetes, or CI/CD.
methodology
- inspect repository deployment configuration, environment ownership, and the exact target before selecting a command.
- use
deployfor a bounded application release; usedevopsfor persistent infrastructure or incident work. - build and test before mutation; use preview/staging where the platform supports it, then promote according to the repository contract.
- verify build/release ID, endpoint status, and one user-relevant behavior. report local, authenticated, and public-production evidence separately.
contents
- trainedrelease evidence and local tool observations
- deployplatform application deploy or publish
- devopsdocker, kubernetes, CI/CD, cloud operation, incident, or security review
- cloudflarecloudflare product-specific configuration
procedures
procedures the guru runs, one page each. read it, then follow it.
- portlessset up vercel portless: removes the PORT requirement for deployments