Yep, that is correct, however I can't figure out how to have a worker *only* be triggered via a serv
Yep, that is correct, however I can't figure out how to have a worker only be triggered via a service worker, and not open to public http requests
HDisable workers.dev, don’t have any routes, or a Custom Domain
CGreat! thanks
CFor
@wrangler-action how can you specify which environment the secrets get applied to? (For a pages project), does automatically figure it out like it does when deploying?
EGuys, regarding Workers <> Neon
What's more performant,
What's more performant,
- utilizing the "prebuilt" way of connecting (think it uses websocket to connect to a neon proxy)
- utilizing raw TCP connection to it via hyperdrive
?
ESince websocket also needs tcp in the beginning I'd imagine the hyperdrive way of doing things to be better
MMaybe a dumb question, but for my worker development environment hosted on *.workers.dev, is it possible to remove my email from the domain (it get's added on by default).
Found the solution, I can change the subdomain
Found the solution, I can change the subdomain
Summ where do i post query about email workers?
H#email-routing
Sthankyou, have raised it there
V@HardlyWorkin'
H?pings
FPlease do not ping community members for non-moderation reasons. Doing so will not solve your issue faster and will make people less likely to want to help you.
AHey everybody,
Is the
Is the
request.signal the complete AbortSignal? I want to react to a request being cancelled request.signal.addEventListener("abort" ()=>{}) , but it wont get triggered? Any clue why?
LI saw the Workers changes and I'm wondering whats up with the Worker to Worker RPC Pricing reduction? Didn't a cloudflare employee say it'll come soon?
URPC hasnt even been out for a month yet "soon" in cf talk generally means at least a few months
UAnd fwiw worker requests are only 30 cents for a million requests even doing like 10 rpc calls is still a crazy good deal
Lreferring to this post. didn't quite make it this weak doesn't sound like months https://twitter.com/irvinebroque/status/1776331933129253290
@sperand_io @elithrar @Cloudflare Two things here:
- We are working on (couldn't quite make it for this week) a change where when you call another Worker via a service binding, this won't be billed as a request. (so that pricing doesn't disincentivize breaking apart an app into many Workers) Coming soon.
4/5/24, 7:31 PM
UI’m aware of the post but still it will probably be a few months for that to be added
KIf you don't read the response body then it will show as cancelled
Npossible to export a whole kv ?
Nfound a way, you cna use the wrangler cli and just redirct the output to a file
HService Bindings don’t pass through the Cache Layer, so you need to invoke the Cache API manually
HIIRC Smart Placement is only used if the first Worker invoked is SmartPlaced
HNot sure then, sorry
JIs there any way to get a longer execution time in a worker than 1 min if it is triggered by cron every 5-10 min?
JI'm seeing this error crop up from time to time:
The destination execution context for this RPC was canceled while the call was still running.
The destination execution context for this RPC was canceled while the call was still running.
SDoes anyone manage to build an email validator with cloudflare workers? to verify whether the email exists or not
MHey guys i am coming back to cloudflare workers after falling down the rabbit hole of nest js server development although really fun and cool, I feel that cloudflare workers was so easy to get going fast. As we stand today can i jump in cloudflare tools like workers, durable objects, and queues to develop a pretty capable platform backend api for something like a ecommerce website with hundreds of thousands of orders per day
