For the past 10 years, I have powered my computer and other office equipment using a pedal-powered generator. I had a website on a shared hosting account that described the project.
I’ve found I’m currently generating enough surplus electricity each day to power our modem and a single-board computer 24 hours a day. (The excess electricity I generate is stored in a storage battery.) So I thought it would be a fun project to host my website on a web server running on the single-board computer instead to create a fully human-powered web site :-).
To reduce hits on my little server and filter out DDoS attacks, I set up Cloudflare as a CDN for the site. I’ve moved the site to my pedal-powered server, and it’s working well except for one problem.
I was hoping that if I was unable to pedal on some days because I was out of town or ill, Cloudflare would serve the entire site from cache. But that does not seem to be the case.
If I open a private browser window and request the landing page from my site (https://www.pedalpc.com), it appears from my server logs that at least one call is always made back to my server. The landing page’s cf-cache-status is returned as DYNAMIC, while all the other content on the page is a HIT.
I have one page rule, for pedalpc.com/*; it’s cache setting is set to “cache everything”.
The caching level under cache settings is set to “standard”, and browser cache expiration is “respect existing headers”. My server currently sets a max-age header for text/html content to be 1 day, which is confirmed in the network section of the developer tools of my browser.
Am I missing something? Will my site always return a 522 error whenever I’m unable to pedal for a day, even if I increase the max-age header on all content well beforehand?