Not sure why it would be hard to maintain a db?
Not sure why it would be hard to maintain a db?
BWell in my situation that would involve creating a central database among 3 different deployment systems, with clashing user ids & script names. Of couse it is achievable, but not an easy task.
BAll that work could be avoided by a single additional option in the binding
UI highly doubt they would do that as it completely defeats the point of namespaces
BHmm, what if namespace ids could be any string and were converted to a number behind the scenes?
If we could use a dynamic string that would solve everything, such as
Knowing which script correlates to which namespace number is the tricky bit
If we could use a dynamic string that would solve everything, such as
namespace_id = "stores/[user-id]/1"Knowing which script correlates to which namespace number is the tricky bit
BYeah agreed, the option to disable it would remove the purpose of namespaces, but that might be useful for some people.
Instead of being at the account level, if they were at the dispatch namespace level for user workers this would also be helpful. It would be easier to maintain a database of ids for user workers in each dispatch namespace than across the whole account.
The option to set a scope level, like account/dispatch_namespace/self might be better
Instead of being at the account level, if they were at the dispatch namespace level for user workers this would also be helpful. It would be easier to maintain a database of ids for user workers in each dispatch namespace than across the whole account.
The option to set a scope level, like account/dispatch_namespace/self might be better
WA namespace is expected to contains thousands or millions of scripts from different customers so I don't think that'll add much more than account level
Wbut yes, I understand the need here. The rate limiting binding is a bit special here in how it works. cc: @tanushree │ Workers PM (for Monday)
YHello,
Is it possible to start tailing a WFP user worker, in the same way as:
https://developers.cloudflare.com/api/operations/worker-tail-logs-start-tail
?
Is it possible to start tailing a WFP user worker, in the same way as:
https://developers.cloudflare.com/api/operations/worker-tail-logs-start-tail
?
Interact with Cloudflare's products and services via the Cloudflare API
BThe API for that doesn't work in WFP. The recommended ways to debug a user worker are with Workers Logpush and Trace Workers.
There was a Google Docs we all got shared in the beta with a walkthrough on how to do it, but some of that information hasn't been added to the Cloudflare site yet. It's not marked as confidential so I assume I can share it here.
The "Trace Workers" in there look identical to Tail Workers, perhaps they are the same thing (renamed from trace to tail?)
There was a Google Docs we all got shared in the beta with a walkthrough on how to do it, but some of that information hasn't been added to the Cloudflare site yet. It's not marked as confidential so I assume I can share it here.
The "Trace Workers" in there look identical to Tail Workers, perhaps they are the same thing (renamed from trace to tail?)
YThanks 
YIs there a way to get a list of active traces?
returns 404:
even though I have some traces, for example calling
returns 404:
even though I have some traces, for example calling
/workers/traces/4ee25b110c9748fd9344790259c7ce73Doing a GET to /workers/traces works for me, it returns an array of all the traces set up
Bhttps://api.cloudflare.com/client/v4/accounts/[account_id]/workers/tracesyep, that's the call I'm making:
I get:
I get:
BStrange, mine is working as expected, and that's not even the error message you get if the trace is not found. It is the error you get if you try to delete a trace that doesn't exist though 
Rhttps://developers.cloudflare.com/api/operations/namespace-worker-put-script-content Is this what we should be using to programattically upload a user's code to a worker on WfP?
Interact with Cloudflare's products and services via the Cloudflare API
Uyes
RInteract with Cloudflare's products and services via the Cloudflare API
BThe first API link you sent is for updating the code only
The second is the one you should use for the initial deployment and if you are changing any bindings
The second is the one you should use for the initial deployment and if you are changing any bindings
Rah i see.. and whats platform_module then ?
RWe ever get an answer for this?
BThat's the name of the file for the example, such as index.js, but theirs is platform_module.mjs
BIt lets a user script import another file uploaded by the platform instead of the user
import { platformThing } from "./platform_module.mjs";ohh ok,. got it situated. thank you
KAs in the shape of the object for the bindings property in your metadata JSON?
K[[dispatch_namespaces]]Creating a dispatch namespace is https://developers.cloudflare.com/api/operations/namespace-worker-create
KA Dynamic Dispatch Worker is just a Worker with one of these bindings
Kin the bindings property of the metadata when you're doing the upload, i.e https://developers.cloudflare.com/cloudflare-for-platforms/workers-for-platforms/reference/metadata/
VI'm trying to work with local development mode and get the following error:
I think it might be missing this bug fix?
https://github.com/cloudflare/workers-sdk/issues/5658
[wrangler:err] SyntaxError: "undefined" is not valid JSONI think it might be missing this bug fix?
https://github.com/cloudflare/workers-sdk/issues/5658
GitHub
Which Cloudflare product(s) does this pertain to? Wrangler core, Miniflare What version(s) of the tool(s) are you using? 3.51.2 [wrangler] What version of Node are you using? v18.19.0 What operatin...
Ron WfP can you use native RPC to talk to other workers on the same namespace? do they have to be service bindings/workers? Just trying to clarify that aspect
BYeah RPC works to the workers in the namespace
Rty
Ralso is it best practises to do 1 R2 bucker per customer? I Assume yes
SOnly if you have less than 1000 customers.
Take a look at https://developers.cloudflare.com/r2/reference/limits/
Take a look at https://developers.cloudflare.com/r2/reference/limits/
RInteresting , I'm sure they mentioned here they could raise limits
RI'm just trying to follow best flow
HThey should be able to
RYeah I don't mind doing one drive and partitioning g with "folder" prefixes per customer either
RYeah looking for confirm on which makes more sense .
RMy next question is, I see serving static from workers is discontinued? So if my users wanted to deploy frontend static htmk or something what would i do?
HDid Sites ever work with Workers for Platforms? The big thing with Sites was just that it had a package/upload tool(Wrangler) that was supported by the team. Everything it can do, you can build yourself
Ryeah it esbuild or something bundles ur frontend into like static assets? thne id do a dist or static folder and like app.servestatic on hono or something, but i saw in thier docs they said it's been dscontinued
RWSites was deprecated many years ago