if environments are abandoned, that means i shouldn't use them, right?
if environments are abandoned, that means i shouldn't use them, right?
Kor should i just always pass production?
Cjust lost the ability to create them/always production
Ceven the dash uses the environments path
Cthere's a good post summarizing it all here: https://community.cloudflare.com/t/environments-vs-deployments/451036/2?u=chaika
Cimportant bit is just that they were called service environments, and had issues with configs/etc, were disabled and never re-enabled, just have production now. The wrangler environments create actual separate workers
Dwhats some realistic latency for a cf api with a small db and a redis cache? i get that this varies a ton but i need to get my latency down as much as possible
Datm i’m using hono, workers, turso, and upstash redis
Di’m just curious about some numbers others have gotten, even if their setup isn’t too similar
AHi
ACan someone deploy nodejs to workers
SHey all, I currently have a Hono server setup with multiple simple CRUD endpoints and to handle for CF queues as well. I want to add an endpoint to handle for websockets with DO.
Is it a good idea to just slap on a new endpoint to handle for the websockets, or should I create a new worker specifically to handle for the websockets and DO?
Is it a good idea to just slap on a new endpoint to handle for the websockets, or should I create a new worker specifically to handle for the websockets and DO?
NI have a Cloudflare Worker that acts as a reverse proxy between various backend services (all proxied by Cloudflare). What options, besides mTLS, do I have to whitelist traffic between the Worker and the backend services while blocking all other requests?
GHi, what auth provider are you guys using?
Ydiscord / steam why ?
H?channel-crossposting
FPlease do not post your question in multiple channels per the rules at #
welcome-and-rules. It creates confusion for people trying to help you and doesn't get your issue or question solved any faster.
welcome-and-rules. It creates confusion for people trying to help you and doesn't get your issue or question solved any faster.NDo you have link?
NFound it thanks! For others it's
cf.worker.upstream_zone (https://developers.cloudflare.com/ruleset-engine/rules-language/fields/)NAny suggestion to do a similar whitelisting from Vercel (not Enterprise) -> Cloudflare Worker?
II'm trying to implement a RPC Service in my auth service worker that verifies a jwt token, but whenever import an interface type from another file, it infers the return type of the RPC to never. But when I turn that interface into a type instead of interface, it does work, why is that?
IIt's a known bug, let me see if I can find it.
IHmmm I can't, @HardlyWorkin' reported it so he probably has the GitHub link
IGitHub
Repro When calling a DO RPC method, return type collapses to Promise/never if using an interface. When using a type, return values are as expected.
I@Isaac McFadyen | YYZ01 thanks, following!
Lhow do i know which zone id my worker needs?
Loh ok zone is a domain, and you get a fake domain using the first part of your email address
Lso, when you create a worker script, you actually get a new route created automatically but that's disabled
Lhow can you enable that from code?
Lmmm
Lapparently there are no zones in my account wut
Li don't get it. you can do it from the GUI but not from code
HDon't know about Terraform specifically, but if you are talking about
workers.dev, it shouldn't be a zoneHIt should be a setting on the Worker itself
Lthat route gets created automatically for each worker
Lif you deploy a script with terraform, it automatically creates the route but it's disabled
Lyou have to manually enable it and then it works
Lbut i don't understand why it works like that
HI don't actually think that setting is covered by the Terraform provider
Lin any case, the
<account>.workers.dev is an actual zoneLi think it's the only way you can trigger your functions unless you register your own domain
HIt is a real zone, but afaik you can't actually add it as a route, you need to do
workers_dev = true in your wrangler.tomlLyeah, you cannot add it as a route
Lif i try to add a route, i see i have no zones available
Lso i'm not sure what that is actually
HIt's a special
HIt's a Zone, but not your zone
HSo you can't actually control it
Lso you cannot have routes, unless you add a custom domain to your worker
HOr use
wrangler/the API to upload