Will I be billed 1 time or 3 times? 1 Dispatch Worker invocation, 2 User Worker invocation
Will I be billed 1 time or 3 times? 1 Dispatch Worker invocation, 2 User Worker invocation
OWe had a client add the _acme-challenge and _cf-custom-hostname txt records as well as the cname records to their dns. However, cloudflare hasn't picked up the _acme-challenge record at all over the past week or so. Just walked them through and got them some new records since the 7 days until expiration was coming up. Is there a reason cloudflare might not be picking up the txt record? The client was using namecheap for their dns if that matters. (Edit: the new txt record isn't getting picked up either, confirmed on the call that it was set up correctly).
OIs TXT validation the same as the DNS validation you mentioned above? Is that the method where we'll have to have our clients renew their DNS records every few months?
OBut this cname record prevents them from expiring?
AThey literally said you won’t get charged for the user worker invocations…
ᎡConsidering building out a rather simple SaaS offering on workers… Looking for clarification/confirmation on a couple things:
‘User Workers’ meaning… These would be workers that I am deploying on behalf of the customer… do customers have visibility of these workers/source code from their dashboard? I presume not (I would hope)
D1 and R2 access from these User Workers… this would be to MY instance yes? And I would be responsible for ensuring segregation of data as appropriate?
Placing limits for customers… This would be something I would need to implement myself from the dispatch worker correct?
‘User Workers’ meaning… These would be workers that I am deploying on behalf of the customer… do customers have visibility of these workers/source code from their dashboard? I presume not (I would hope)
D1 and R2 access from these User Workers… this would be to MY instance yes? And I would be responsible for ensuring segregation of data as appropriate?
Placing limits for customers… This would be something I would need to implement myself from the dispatch worker correct?
W‘User Workers’ meaning… These would be workers that I am deploying on behalf of the customer… do customers have visibility of these workers/source code from their dashboard? I presume not (I would hope)
They do not, you give as much visibility as you want on your own platform
D1 and R2 access from these User Workers… this would be to MY instance yes? And I would be responsible for ensuring segregation of data as appropriate?
correct
Placing limits for customers… This would be something I would need to implement myself from the dispatch worker correct?
correct
ᎡCool looks like I got my head on right lol.
Also, regarding serving pages/ui to customers… would this be better purely within a worker or durable object? Or could say a crafty Pages project be repurposed dynamically via the User Workers?
Also, regarding serving pages/ui to customers… would this be better purely within a worker or durable object? Or could say a crafty Pages project be repurposed dynamically via the User Workers?
W
What exactly is the tag (not tags) field on the script object?https://developers.cloudflare.com/api/operations/namespace-worker-script-worker-details
JHey all! Currently setting up a project for external script to be ran by my customers following the default example https://github.com/cloudflare/workers-for-platforms-example
but got alittle caught up everything seems to run the database stores and the dispatcher seem to be created but I think my question is around the outbound workers! Do I need to setup a default one for the users script to attach to? and or am I running down the wrong direction? I was under the assumption this hono server was the default dispatch worker and would return the result from the script!
but got alittle caught up everything seems to run the database stores and the dispatcher seem to be created but I think my question is around the outbound workers! Do I need to setup a default one for the users script to attach to? and or am I running down the wrong direction? I was under the assumption this hono server was the default dispatch worker and would return the result from the script!
GitHub
A great place for platforms to get started on Cloudflare Workers! - cloudflare/workers-for-platforms-example
JAm I wrong here?
JAny help is much appreciated 
JI was thinking it would work something like this but internally from that apt do i just need to ensure the dispatcher name-space matches?
JFigured it out 
J
J
JI had capitalized the binding from the intial demo to my wangler config and wasnt able to find it correctly!
BHey does anybody here have experience stackblitz or some sort of "browser ide" to allow customers to create worker code?
YHey,
We're using the workers for platforms, and I want to monitor the number of
Can you please recommend the best practice for that?
I'm playing with the Graphql api, but cannot really find the best match to count the number of scripts (we have our users creating many of workers, and I want to be able to monitor that)
Thanks!
We're using the workers for platforms, and I want to monitor the number of
Workers for Platforms Scripts (I have this section in our bill).Can you please recommend the best practice for that?
I'm playing with the Graphql api, but cannot really find the best match to count the number of scripts (we have our users creating many of workers, and I want to be able to monitor that)
Thanks!
DI'm confused a bit, is "cloudflare for saas" a feature of "workers for platforms"? I'm trying to setup (the third time 
) custom hostnames so that customers can point their domain to my worker. But I can't get this to work. The fallback origin is a worker, I've setup the
So do I need an activate "Workers for Platforms" (meaning do I have to upgrade my page plan in order to enable it?)
) custom hostnames so that customers can point their domain to my worker. But I can't get this to work. The fallback origin is a worker, I've setup the AAAA 100::, origin seems fine, hostname added, validation completed – but when I access the customer domain (that should be now pointing to my fallback origin (worker)), I always get a cf page with 522. So do I need an activate "Workers for Platforms" (meaning do I have to upgrade my page plan in order to enable it?)
DHi, are the docs for local development up to date? https://developers.cloudflare.com/cloudflare-for-platforms/workers-for-platforms/get-started/developing-with-wrangler/
The
The
wrangler@dispatch-namespaces-dev release seems to be 4 months old
RHas anyone manage to get aws sdks to work in Tail Workers? workers-and-pages-helpAWS SDK in Tail Worker?
B
DRight, I’m just wondering since that dev package is so old, would it be significantly behind what’s currently latest on npm?
AHow I change Change My Website FIles In Workers And Pages
Dwokrers for platforms can use eval?
INo. Eval is prohibited on all Workers, even WfP.
IWhat you can do on WfP is upload a Worker via the API and then run it from your dispatch Worker - so kind of like a slower eval.
DSo make a new workers per script?
IYes, a new Worker on Workers for Platforms.
D:rip:
IThe idea with WfP is you can deploy many many Workers (the usual limit of 100 doesn't apply)
D@Isaac McFadyen | YYZ01, EWR01 do you know if you can reset/have fresh context on every worker execution
Dfor example
Di make a global
Di dont want that global to exist on the next exeuction
Dfresh context
IIn general you shouldn't be using globals for this reason... what do you need a fresh context for?
Dso like sandbox
IAs in, you are running user code and the user code might store a global?
Dmy codebase uses globals
Dand i cant port it over to be localized
Di want fresh init each time
Di think workers cached it last time i tested
IAs far as I know this is not possible. Creating a whole new global state is quite expensive (relatively speaking), so Workers tries to minimize it as much as possible by not resetting global state every request.
Droger that
RHas anyone run into an issue where they use RPC https://developers.cloudflare.com/workers/runtime-apis/rpc/ and everything works as expected, but the logs for the RPC worker report an outcome of
canceled ? Also reported here but with no answers https://community.cloudflare.com/t/outcome-canceled-with-status-of-200-is-this-dangerous/653874 (context - I am calling an RPC worker from a user worker).Cloudflare Docs
The built-in, JavaScript-native RPC system built into Workers and Durable Objects.
