You can ignore that for secrets

does it want this

like me listing them

or what

its hard to understand what it wants

or ok i guess i ignore

This example is simply showing the secrets commented out in your wrangler.toml, so anyone else looking at it knows which secrets they should specify - and you don't have to do this if you don't want to

Anything not commented out in the [vars] section is a regular (non-secret) env variable, that you include in the file normally

Hey @dave - did you get answer to this question?

I think it streams instead of buffers by default, based on the fact that waiting until fully buffered is an enterprise feature.

we ended up going all-in on S3 APIs 😛

FYI requests are fully buffered by default. The request is not sent to your server before the client has finished sending the entire body.

oh interesting, didn't know uploads were different than downloads!

Downloads aren't buffered unless you are on Enterprise and enable Response Buffering.

The reason for buffering requests is so WAF can run on the request body.

Ahhh yes, that makes sense!

that also sorta makes sense why there's a 100MB limit

It's also to prevent slow loris attacks

Usually, disabling request buffering is only done for Enterprise customers, but I believe - though don't quote me on this - that PAYGO customers can get it disabled if they ask nicely and are lucky. There's nothing about unbuffered uploads that inherently makes it Enterprise only. If anything, it reduces load on Cloudflare.

I'd like to create multiple workers within the same project, is the wrangler.toml a 1:1 relationship per worker?

It is, yes. You'd almost certainly want a separate wangler.toml per worker

Gotcha! thanks

Is it possible to have a worker explicitly execute in 3 different locations at the same time? I'm creating a dashboard that's monitoring a public API and would like to account for geo differences

Not really, no. Workers deploy everywhere. If you have 3 VPSes in those regions, you could hit the worker from those locations. With Smart Placement (https://developers.cloudflare.com/workers/platform/smart-placement/), the Worker will move to a specific region if it makes sense (due to hitting a regional DB multiple timese for example), but that's also not really what you want it sounds like.

Cloudflare has a specific healthchecks product though that you can use to hit stuff from specific regions - perhaps that would be more suited?

You can also use a DO(with some trial and error), or a Load Balancer Health Check(might be Enterprise only)

What James said

ah so i'm just doing this as a personal project, and it's not actually my API