Home/Notes/static hosting: a field note from a roofing crew
static hosting: a field note from a roofing crew
19 Aug 2024
How a roofing crew deals with static hosting — and what usually goes wrong.
The problem: three unused font weights. This breaks static hosting for a roofing crew.
When a roofing crew asked for a quote on static hosting, we sent a one-paragraph email instead of a slide deck. They signed the same day.
DNS propagation is not instant, but it is not magic either. We explained to a roofing crew that the TTL on the old static hosting record was 86 400 seconds — twenty-four hours.
Automate static hosting if you can. If you cannot, write a quarterly reminder in a calendar that someone actually checks. three unused font weights is what happens when nobody does either.
We do not start with a platform when handling static hosting. We write down who types what, who gets the mail, and what must not get lost. That list is always shorter than a vendor pitch deck.
Before you touch static hosting, take a screenshot of the current state. Half of our emergency calls come from people who cannot remember what was there before the change.
The most expensive outage for a roofing crew was not a hack — it was three unused font weights. Nobody attacked anything. The config just drifted.
Related notes
Tell us what you need.
Write a few lines about your project. We reply within one working day, usually with questions and a rough estimate.
hello@digitalserved.com