okay so same response? well anyways I think you could just add some random

sleep()

calls or something right?

yeah, my thought is my only solution is to make it a fixed time :/

do a setTimeout and make that finish before returning

we store our API key and user usage info entirely in DO which is so fast I don't think we really have this issue

but I might be (probably am) missing something

wouldn't they need to send a valid API key or credentials before you call AWS though?

we are the AWS API endpoint 😛

I figured it out, thank you! This message made me question things a bit... realized it's because you're using just an API key, while I am using an API key + username. I think I figured out how to optimize down to just 1 piece of creds that I can verify in the backend.

Should worker sites be considered deprecated? It seems like their functionality has been subsumed into Cloudflare Pages

Yes, pretty much. It still works and there's patches every now and then, but it's not actively developed anymore.

I would default to Pages, and then consider Sites if you run into a use-case that really needs it. Where Sites still has a place imo, is large complex apps with features that Pages doesn't natively support yet, like Queue consumers, Cron triggers, etc.

Is the download performance (using bucket = ./example) for users as good as the user experience provided by pages btw?

And it drives me crazy that there's no documentation for how Pages interacts with wrangler.toml! That alone is tempting me to use Sites

wrangler.toml

is a Workers things. Pages doesn't use it at all. If it does in dev, that's not intentional.

But I agree, the lack of any real config for Pages is pretty sucky DX.

Oh, you're right. Sorry about that confusion

But yeah, I do really want a config file

Sites performance vs Pages is gonna be pretty negligible - they both use the same underlying technology which is KV.

I thought they would have used R2 and the cache api

I know it's cheaper anyhow

R2 didn't exist when Pages was made 😉

and KV has great hot read times

There's no way I could build my own Cloudflare Pages from scratch at the same price of essentially free

Cloudflare Pages: 12/17/2020 Cloudflare R2: 09/28/2021

from the blog post announcements

I want incremental asset updating, rather than full folder uploads, which I guess means I'd have to create on my own using KV. Only downside is the price

Is there harm in just uploading all at once?

And the work hahaha

I have a slow refresh process for what I'm hosting.

I don't have all the assets all at once. It probably will be fine