What's the best way to develop locally for WFP with Wrangler? :monkaThink:
What's the best way to develop locally for WFP with Wrangler? :monkaThink:
WIt seems like it should be uploading a
multipart/form-data
Mdocs are incoming, but as of right now there's a prerelease Wrangler branch
wrangler@dispatch-namespaces-devyup!
--remote
RYes my next question was how we should test users workers before deploying
WMy recommendation for user Worker logs is enable logpush and send them to Baselime
Wor you can attach a Tail Worker and send them anywhere/manage them as you want 
Mhere's some docs for local development https://developers.cloudflare.com/cloudflare-for-platforms/workers-for-platforms/get-started/developing-with-wrangler/
this wrangler prerelease branch is experimental, but we're looking to solidify this and get it in soon
this wrangler prerelease branch is experimental, but we're looking to solidify this and get it in soon
Cloudflare Docs
To test your Dispatch Worker, user Worker and Outbound Worker before deploying to production, you can use Wrangler for development and testing.
RThanks .. next I'm looking for a good API or to build one for esbuild so I can build customer workers w imports etc.
NCheck out https://esb.denoflare.dev
Roh wow ! Is this reliable ?
Nin my experience it is ... it's run by @John Spurlock
RTy
BSeems like old scripts cant be deleted with error
I tried deleting one which was uploaded a few months ago but it fails, however when I tried (the same way) deleting one that was uploaded this week it worked fine. I tried with the force flag too.
workers.api.error.unknownI tried deleting one which was uploaded a few months ago but it fails, however when I tried (the same way) deleting one that was uploaded this week it worked fine. I tried with the force flag too.
UAre you on enterprise or did you get it on pay-go before the plan released? Either way sending an account id can probably help an employee look at it when they see it
BEnterprise & access through tanushree. I was able to resolve it by uploading a new script with the same name then deleting it.
Rwheres the link for buying WfP ? or upgrading from paid workers to that
AClick it in navigation on the dashboard and then the button to sign up..
Ryah im not seeing it on my other account hm
BI don't see the option to delete secrets in Workers for Platforms API docs. How do you delete secrets using the API?
BThis should work
BWell it's meant to work but it has an
workers.api.error.unknownThanks. Yes, I tried this before; I got the same error. Another issue I noticed is I can't access the "cf" request object in user workers.
Rreally? So their workers don't image access to the cf request object from the context ?
RIs that by design
BYeah the API seems to have a few issues unfortunately.
As for the cf props, something similar happens on DOs too - see the explanation of why here: durable-objects
If your project doesn't have a strict requirement of using the "fetch" entry point you might be able to use RPC to pass it down to the user worker (I've not tested this though)
As for the cf props, something similar happens on DOs too - see the explanation of why here: durable-objects
If your project doesn't have a strict requirement of using the "fetch" entry point you might be able to use RPC to pass it down to the user worker (I've not tested this though)
BI will check this. I have passed "cf" fields as request headers - as a quick fix.
BThere's a workaround I just figured out for deleting secrets, you can use the 'Patch Script Settings' API with a new array of bindings and it'll replace all the existing bindings with the ones specified. If you have other secrets you'd have to define them again which is a bit annoying
BI think patching does not have effect on secrets that are not included in the bindings array.
BIt did when I just tried it
BAh yeah you are right, it's actually still there but doesn't show as there in the API, strange
BThey even remain if you delete the script & upload it again, so I guess they're impossible to remove for now
AHey Folks,
Can a user worker be a consumer of a queue? if so how can I configure it?
using this configures the user worker as a producer, but not a consumer.
Should I use the dispatcher as the consumer and then route those messages to the user worker from there?
The issue there would be they will change to be fetch events instead of queue events as there's only
Can a user worker be a consumer of a queue? if so how can I configure it?
using this configures the user worker as a producer, but not a consumer.
Should I use the dispatcher as the consumer and then route those messages to the user worker from there?
The issue there would be they will change to be fetch events instead of queue events as there's only
userWorker.fetch
BYou asked this one before, and the answer is still the same unfortunately.
The issue is that the API to create a consumer on a queue doesn't support referencing to dispatch namespace workers. Consumers are configured on the queue rather than the worker.
The only way for now is to create a regular worker that dispatches it to the user worker. You can use RPC to pass it to a handler other than fetch
The issue is that the API to create a consumer on a queue doesn't support referencing to dispatch namespace workers. Consumers are configured on the queue rather than the worker.
The only way for now is to create a regular worker that dispatches it to the user worker. You can use RPC to pass it to a handler other than fetch
Mcomplete noob question, but I wasn't getting smart out of the docs: do user workers support scheduling?
UI assume you mean cron triggers? I would assume they do but have not tested myself.
UAnd if by scheduling you meant very specific time instead then you can use durable objects to make alarms to support invoking at a specific time
DHey, beginner question that maybe someone here can help me out with.
I'm going through the basic "Getting Started" docs of WFP, got a namespace, a user worker and a dispatcher.
So far everything works. Now, i've updated my dispatcher to be a dynamic dispatcher which by the docs is supposed to receive calls to
It doesn't say in this part of the docs how i should have configured my dispatcher's domains / routes for this to work, can someone help me understand what i'm missing?
Thanks.
I'm going through the basic "Getting Started" docs of WFP, got a namespace, a user worker and a dispatcher.
So far everything works. Now, i've updated my dispatcher to be a dynamic dispatcher which by the docs is supposed to receive calls to
<USER_WORKER_NAME>.<MY-DOMAIN>.com/**.<MY-DOMAIN>.com<MY-DOMAIN>.comIt doesn't say in this part of the docs how i should have configured my dispatcher's domains / routes for this to work, can someone help me understand what i'm missing?
Thanks.
