Multi-Cloud Deployments with GitHub Actions
summary
A real migration from two monoliths to a mono repo with four sites uses GitHub Actions, reusable workflows and path-based triggers to avoid rebuilding everything on every commit. The setup builds an ASP.NET 6 -> Azure Web App for the interactive MVP and three Next.js -> Vercel heads, pushes content to XM Cloud (SaaS CMS), runs staging then prod via workflow_dispatch or main-guarded steps, and yields targeted, working deployments.
AI-written summary · about
chapters (13)
- 0:00Multi-cloud deployments intro
- 1:36Legacy monolith challenges
- 3:19Unified mono repo benefits
- 5:25GitHub Actions for CI/CD
- 6:29Splitting pipelines by system
- 7:13Workflow structure and naming
- 8:18Targeted deployment config
- 10:03Building .NET apps
- 11:28Azure Web Apps deploy
- 14:37Next.js to Vercel deploy
- 17:51Community actions leverage
- 18:55Monitoring in GitHub UI
- 21:20Key takeaways
related talks
42mPipelines, IaC and Deployments with Github Actions & Octopus Deploy
43mAzure DevOps and GitHub Actions
01h 01mGetting Started with GitHub Actions
44mLevel-up Your DevOps with GitHub Actions and Kubernetes
36mAzure Static Web Apps
29mShip it with GitHub Actions and GitHub Packages
01h 00mMoving 17 years of old legacy code and sites into the Cloud
38mLevel-up Your DevOps with GitHub Actions & Kubernetes
