PS: if you go in the Datacenter Stats page it will give you a breakdown of POPs for a bunch of website we have figured out the approximate plan. It's still a pre-alpha over there, but it may help you @User.

Pick and choose the provider 🤭 https://github.com/adaptive/pops

Oh, wow. That is great!

It's only missing a city name for user consumption... unless you add a IATA code list, but that is big.

No city names is by design, you have IATA, and Latitude and Longitude, the purpose is latency inference and plotting.

Oh yeah, for sure. It's also smaller and can be augmented if needed. It makes total sense for a general list 🙂

I just wanted to give a shout-out to the amazing team! You‘re doing an amazing job! Thank you for your hard work 🖤 Also, love the idea of using discord 🙂

Discord better than Teams or something else because they're an enterprise customer

I see you blog post @kristian 😉

Nice! Planning om building an ecommerce solution myself 🙂

someone managed to write to redis directly from a worker? 🙂

Sharing my most recent use-case for Workers and HTMLRewriter 🙂 https://jross.me/progressively-delivering-new-image-formats-with-css-and-cloudflare-workers/

WOAH @User this is sick

this reminds me of something I would add to https://github.com/signalnerve/ggf 🙂

Thanks 😄 I spent longer than I care to admit trying to find a solution with just CSS, but as far as I can tell, it's simply impossible today.

And definitely, it would be a great addition there.

morning everyone 🙂

Does anyone here know if there is a way to have a prod and a staging Workers Site?

Two different scripts and deployments

You’d need to use a different wrangler.toml configuration

Changing the zone id and/or routes

I was kinda hoping it would be something as cool as the deployments for the normal Workers, just not documented 😦 Thanks for the confirmation.

What would you like to see done differently?

Something to the tune of so that I can deploy without bringing down the main worker and check if everything works (or to preview a new layout, etc.):

[site.staging]
// all the options

[site.prod]
// all the options

Interesting idea @kristian what do you thing about wrangler publish [zoneNickname] for selective pushing?

That’s an interesting idea admittedly it’s not as seem less currently. Unit testing helps here 😉

Sure, but if you are doing a new version of a website and you are working in a different branch using environments works better. With unit testing you may catch usability issues, but maybe you need to show others the work or need feedback (or your are providing a beta for the users).

we're working on a solution for this, will be able to give you more details soon 👀

shouldn't

wrangler publish -e

cover this or am i misunderstanding?