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 tail
THey 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 
Ruse one KV
Rand preface each like customerId_KeyName
TYou should create 1 KV namespace per customer (would recommend the same practice for D1, R2, etc). We can increase limits as needed
KIf i create a user script and delete it after 5 minutes does that incur the full 0.02 charge?
DGood question :monkaHmm:
RIs this the best practices then? One KV namespace per user
WDepends on the use case but if you're just providing these to users then yes definitely
WIf this was a namespace where you control the reads then one namespace overall is ok
RYes it's for users. That's why I was hoping that's the route but ok thank you
KI'm hoping for it be pro rated hourly or something similar 
WI haven't tried the JS SDK for this yet, let me take a quick look at the code and see if I can figure out what it's doing
DWhat's the best way to develop locally for WFP with Wrangler? :monkaThink:
WIt seems like it should be uploading a
multipart/form-data but we don't seem to be seeing that
Mdocs are incoming, but as of right now there's a prerelease Wrangler branch
wrangler@dispatch-namespaces-dev that enables local dev for dispatch namespacesMyup!
--remote will work fine, but you'll be dispatching to live user workers at the edge. we have complete local support incoming, where you dispatch to other locally running user workers
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.
