News for hackers. Stuff that matters.
Re:Native Rust Support on Cloudflare Workers by junon on Thursday September 09, 2021 @09:46AM (#28469613)
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.

Re:Native Rust Support on Cloudflare Workers by WORMS_EAT_WORMS on Thursday September 09, 2021 @10:56AM (#28470387)
Same 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

[2] https://github.com/cloudflare/kv-asset-handler

Re:Native Rust Support on Cloudflare Workers by ec109685 on Thursday September 09, 2021 @10:10AM (#28469879)
Is that loose cache based on the KV propagation delay?
Re:Native Rust Support on Cloudflare Workers by junon on Thursday September 09, 2021 @10:37AM (#28470162)
I would imagine so, yeah. Hard to say definitively.