Multi-Site Fleet: Pins, SSL, and One Go-Live at a Time

Fleet is how sites actually die

A pin bump, a shared runner, a leftover squash. We treat each public hostname as a release unit.

What we operate

DNS, TLS, workers or containers, OG/meta, forms, backups. Status is curl, not a spreadsheet.

ASAP vs retainer

Fire today is this desk. Ongoing fleet is Oniyore ops. Same people, different clock.

Inventory first

Send the list of hostnames. We say which are live, parked, or NXDOMAIN.

Questions

Do you rebuild every site on one framework tonight?

No. We stabilize what is live, then migrate on a train.

Can one bad PR take all sites down?

Not if we do not share a cancel-in-progress deploy group across unrelated hosts.

More notes

• Website Down Today: What We Fix in the First Hour
• SSL Certificate Expired: Browsers Block, Calls Stop
• Contact Form Not Sending: The Quiet Lead Leak
• DNS Cutover Same Day Without a Mystery Outage