A site that is fast and stays available rests on infrastructure choices that are rarely visible from the home page: where the files are hosted, how they are delivered, what exactly happens when the server stops responding. This section deals with all of that without needless jargon. We cover setting up a content delivery network and security rules with Cloudflare, choosing and sizing a server, certificates, domain names, off-site backups and emergency failovers. A second strand is given over to troubleshooting proper: diagnosing a site that cannot be reached, bringing a damaged database back up, making sense of a traffic spike, getting out of a lock-up after a botched update. Finally, we describe how we work through support tickets, what a ticket covers, how to write one so that things move quickly, and what instead calls for a longer intervention to be planned together.
Critical error, white screen, error 500: the step-by-step route to finding the cause, getting the site back online and not making the outage any worse.
CDN, caching, application firewall, certificates: what Cloudflare really brings to a site, the settings that matter and the configuration traps to avoid.
A backup that has never been restored is not a backup. Frequency, retention, the 3-2-1 rule and the restore test: the method that lets you sleep soundly.