← Graph

Write an explicit go-live runbook

takeaway 1 connections

Go-live advice: inform clients, find a low-usage time (e.g. Saturday 5am), schedule a maintenance window in advance, write a runbook with exact commands, tests and checks, assign each step to a person, and define a contingency/revert plan in case something goes wrong. Use DNS records as the final flip trigger after everything else is deployed and tested.

type
recommendation
takeaway Write an explicit go-live runbook
from_talk
Miron's go-live planning advice including contingency and DNS-flip trigger.

Provenance