Deployment Runbook – BlazorChat Demo

Why is chat next to a runbook? BlazorChat provides the chat widget — your app provides everything else

Scoped, persistent conversation

During a deployment your team is already talking — in Slack, Teams, or on a bridge call. BlazorChat ties that conversation directly to this release thread (deploy/v2.4.1/prod), so every decision, blocker, and sign-off is captured alongside the step it belongs to. No context switching, no lost history.

One connection, two real-time streams

Because BlazorChat uses SignalR, the same connection that delivers chat messages could also broadcast live step-status updates. Alice marks step 7 complete — every engineer watching this runbook sees it instantly. The runbook data here is static to keep the demo self-contained; in a real integration the host application owns the data.

LoneWorx Portal v2.4.1

PRODUCTION

6 / 14 steps complete

Build #1847

Target portal.loneworx.com

Window Feb 22, 2026 · 02:00–04:00 UTC

CAB Ticket CHG-0042

Lead Alice (DevOps)

Status ● In Progress

Deployment Steps

#	Step	Owner	Est.	Status
Pre-Deployment 4 / 4
1	Notify stakeholders of maintenance windowEmail sent to portal-ops-dl at 01:45 UTC	Alice	5 m	Completed
2	Create database backup (portal_prod)	Carol	10 m	Completed
3	Verify feature flags: portal.dark-mode, portal.v2-api	Bob	5 m	Completed
4	Confirm CI/CD artifacts — build #1847, all checks passed	Carol	5 m	Completed
Deployment 2 / 5
5	Enable maintenance page	Alice	2 m	Completed
6	Run database migrations (11 scripts)	Carol	15 m	Completed
7	Deploy API services (v2.4.1) — 4 pods3 of 4 pods healthy — pod api-4 restarting	Carol	10 m	In Progress
8	Deploy frontend assets (v2.4.1) to CDN	Bob	5 m	Pending
9	Warm up application caches	System	5 m	Pending
Post-Deployment 0 / 5
10	Run smoke test suite (73 tests)	Bob	8 m	Pending
11	Monitor error rate for 10 minutes	Alice	10 m	Pending
12	Verify health-check endpoints (/health, /ready)	System	3 m	Pending
13	Disable maintenance page	Alice	2 m	Pending
14	Notify stakeholders — deployment complete	Alice	5 m	Pending

Release Chat [deploy/v2.4.1/prod]

6:00 PM

Starting the v2.4.1 deployment. Maintenance window is open. Everyone on the bridge?

Bob (Frontend) 6:01 PM

Here and ready 👋 Feature flags confirmed — portal.dark-mode and portal.v2-api both verified.

Carol (Backend) 6:02 PM

DB backup complete ✅ portal_prod snapshot taken at 02:03 UTC. Safe to proceed.

👍 2

6:03 PM

Enabling maintenance page now.

6:04 PM

Maintenance page is live. Kicking off the 11 migration scripts.

Carol (Backend) 6:05 PM

Running migrations...

Carol (Backend) 6:20 PM

Migrations complete ✅ All 11 scripts applied cleanly, zero errors.

🎉 2

6:21 PM

Deploying API services now. Watching pod health.

6:28 PM

⚠️ pod api-4 is in a restart loop. Pulling logs.

👀 1

Bob (Frontend) 6:29 PM

Alice (DevOps) ⚠️ pod api-4 is in a restart loop. Pulling logs.

Could be the config map — saw something similar on the staging run last week.

💡 1

Carol (Backend) 6:30 PM

api-1, api-2, and api-3 are healthy and serving traffic.

6:31 PM

Bob (Frontend) Could be the config map — saw something similar on the staging run last week.

Confirmed — stale config map reference in the api-4 pod spec. Patching now.

6:33 PM

Patch applied. Watching api-4 come back up...