Serving for the win - Deployments and hosting for the rest of us
summary
Tells how deployments move from fragile FTP drag‑and‑drop to scripted CI/CD: Git tags auto‑build with Jenkins into Google App Engine so every version has a stable URL for QA, translations and launch; Netlify ties Git → build → CDN and surfaces pull-request previews for review; embraces the JAMstack, APIs at build or run time, and routing traffic between versions to enable immutable deploys, repeated safe launches, easier rollbacks and genuine A/B or localization experiments.
AI-written summary · about
chapters (11)
- 0:00Start
- 1:20CRUSHER
- 3:46FUNDAMENTALS
- 5:50SLEEPLESS NIGHTS
- 9:03INFRASTRUCTURE
- 10:12NEW DEPLOYMENT CONVENTIONS
- 10:23APPROACH
- 13:49UNREPEATABLE PROCESS
- 18:36VERSION CONTROL
- 19:15AITCH TEE TEE PEE DOUBLE MEH
- 32:31USE THE SKILLS OF OTHERS
related talks
43mServing for the win - Deploys and hosting for the rest of us
25mDemystifying deployments as a service
08mHow Your Architecture & Infrastructure Can Make or Break Your Team’s Productivity
43mContinuous Deployment: The GitOps, The Pipelines, and The Ugly
36mCI/CD in a Serverless World
34mDeploy, Release, CI/CD, Oh My! DevOps for the Rest of Us
30mImplementing Continuous Deployment with Jenkins & Gerritt
22mLet's Build A CI CD Pipeline