3 ms·
I host static content with them (with no fallback server) using their keyval stores. All GETs result in a KV lookup. A PUT uses a signed payload and a set of p
by junon 5y ago
I host static content with them (with no fallback server) using their keyval stores.
All GETs result in a KV lookup. A PUT uses a signed payload and a set of public keys in another KV store to check that the caller is allowed to store the new page contents.
I can re-deploy a site in a matter of milliseconds and it is only loosely cached (updates are reflected within a minute or so), free for up to 100k requests a month, and serves content in a matter of milliseconds.
- ec109685 5y agoIs that loose cache based on the KV propagation delay?
- junon 5y agoI would imagine so, yeah. Hard to say definitively.
- WORMS_EAT_WORMS 5y agoSame except I go POST and version the assets. It's a super fun and awesome way to manage sites IMO. The idea is what Worker Sites [1] do via KV Asset Handler [2]. Would love to see your code for signed Payload / auth. Or, just hear how you do it. My auth is a bit... weak. Cheers. [1] https://developers.cloudflare.com/workers/platform/sites https://developers.cloudflare.com/workers/platform/sites [2] https://github.com/cloudflare/kv-asset-handler https://github.com/cloudflare/kv-asset-handler