Home/Notes/How a restaurant should handle static hosting
How a restaurant should handle static hosting
11 Mar 2025
How a restaurant deals with static hosting — and what usually goes wrong.
The problem: a plugin login nobody has used since March. This breaks static hosting for a restaurant.
We got a call from a restaurant on a Friday. Their static hosting had expired overnight, and the booking page was returning errors to every visitor.
Instead of migrating static hosting all at once, we ran both configurations in parallel for a week. The switch happened on a Wednesday morning — the quietest traffic window.
The worst static hosting failure we have seen at a restaurant was invisible for eight months. The backup existed but had never been tested, and the data inside was three migrations old.
The fix was to delete the old entry, wait for TTL to expire, and re-add static hosting with the correct value. We scheduled it for 3 AM so nobody lost traffic.
A free certificate and a correct static hosting record will do more for a restaurant than a redesign that ships with a plugin login nobody has used since March still in place.
After fixing static hosting, we added a monitoring alert. If the record changes or the certificate approaches expiry, both we and a restaurant get an email. No surprises.
We hand over a one-page document after every static hosting job. It says what was changed, what the login is, and what to check if something feels wrong. a restaurant keeps it in a drawer they actually open.
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