What a florist needs to know about backups

We rotate API keys for backups annually. a florist did not see the point until we showed them the access log: the old key had been used from an IP in a country nobody on their team has visited.

We keep a playbook for backups. Step one is always the same: pull the live record with dig, compare it to what the admin panel shows, and fix the mismatch.

Launch day for a florist is usually light. Week three is when leftover tags, fonts, and staging URLs show up. three unused font weights is the usual passenger.

The vendor portal had silently rotated the key for backups, but a florist was still using the old one. Every outbound message bounced quietly.

Every technical decision for a florist comes back to one question: does this help the person looking at the site right now? If backups is invisible to that person, it is working.

More notes

Related notes

• What a dental office needs to know about backups
• A practical look at backups for a veterinary clinic
• backups: a field note from a roofing crew
• A practical look at backups for a print shop