A static cost per script is easier to calculate which is why it’s that way
A static cost per script is easier to calculate which is why it’s that way
Kyeah makes sense, thanks
KIf i create a user script and delete it after a week does that incur the whole 0.02 charge?
WWe would need to add a way of saying it's a Workers for Platforms script. Probably most likely is having secret put under wrangler dispatch-namespace so you'd do
wrangler dispatch-namespace secret put <secret-name>cc: @tanushree │ Workers PM
Ryeah i was curious on the same, if we can store secrets for a customers worker
WYeah in the UI we don't let you modify script bindings iirc
WYou can use the API but yeah we should add to wrangler for sure
BYou need to do it by API, but as Walshy said we should add an namespace option to wrangler similar to the deploy script
Here's an example of the API method
Here's an example of the API method
RWhat are the list of type For that
Dhere's some of them that are documented: https://developers.cloudflare.com/cloudflare-for-platforms/workers-for-platforms/reference/metadata/
I usually check wrangler's source code for the others
I usually check wrangler's source code for the others
RTy
Ris it stll not advised to do 1 namespace per "customer" ?
UA namespace can have unlimited scripts you should be giving them tags if you want to list by a customer or saving in your own db
Ryah ive seen mixed , some recommended 1 per customer other ssaying do all on same one and use tags.. if i wanted a user to have their own "kvs" those would all just be on the same namespace also right?
PKV is different to workers for platforms, and you can only have 100 KVs in your account unless you request a limit increase.
Unless you have less than 100 users or can get an increase approved, you are best to either use one KV and prepend a customer ID to each key, or you could also utilize Durable Object's Transactional Storage API, which works on WfP and is similar to a KV (just not as good performance wise).
Unless you have less than 100 users or can get an increase approved, you are best to either use one KV and prepend a customer ID to each key, or you could also utilize Durable Object's Transactional Storage API, which works on WfP and is similar to a KV (just not as good performance wise).
ROk that's good too so one for all customers
TExited to get this out! We're just waiting for a release in the afternoon (US time), after then it will be available
D
THaha the anticipation builds. It's coming!! We're waiting on another team's release (I'm told its in progress)
TYou'll see a new tab in the dash under "Workers & Pages"
TI can spare you - I'll shout on discord once it's up!
Bkeeps refreshing the dashboard
TSorry to dissapoint y'all. Our team has a snag with the release and they're still working on it. I'll be sure to follow up here once we're in the clear
Wp.s. do 
/subscribe Workers for Platforms
BIs there anyone here who could help me
D?ata feel free to just post your question and when someone can, they will answer
F
BSomething like this
DAre you using Workers for Platforms? If not, please use another channel like #workers-help and show us what error you see when you run
wrangler tailHey everyone! Excited to share that we’ve released Workers for Platforms 
You should see a new “Workers for Platforms” tab under the “Workers & Pages” tab.
If you’re not seeing it — please DM me your account ID. We have some moving pieces behind the scenes and we may not have gotten to your account yet.
You should see a new “Workers for Platforms” tab under the “Workers & Pages” tab.If you’re not seeing it — please DM me your account ID. We have some moving pieces behind the scenes and we may not have gotten to your account yet.
W
DI don't see a new tab :monkaThink:
WPlease DM @tanushree │ Workers PM with your account ID
