Hey does anyone knows how to upload a script via API? I'm trying: ```js const main = ` export def

Hey does anyone knows how to upload a script via API?

I'm trying:

const main = `
export default {
    fetch(request) {
        return new Response('Hello World');
    }
} 
`
const metadata = JSON.stringify({ main_module: "main.js" })
const formData = new FormData();
formData.append('main.js', new Blob([main], { type: 'application/javascript+module' }))
formData.append('metadata.json', new Blob([metadata], { type: 'application/json' }))
return await $fetch(`${baseUrl}/namespaces/timo/scripts/hello`, { method:"PUT", body:formData, headers })

const main = `
export default {
    fetch(request) {
        return new Response('Hello World');
    }
} 
`
const metadata = JSON.stringify({ main_module: "main.js" })
const formData = new FormData();
formData.append('main.js', new Blob([main], { type: 'application/javascript+module' }))
formData.append('metadata.json', new Blob([metadata], { type: 'application/json' }))
return await $fetch(`${baseUrl}/namespaces/timo/scripts/hello`, { method:"PUT", body:formData, headers })

const main = `
export default {
    fetch(request) {
        return new Response('Hello World');
    }
} 
`
const metadata = JSON.stringify({ main_module: "main.js" })
const formData = new FormData();
formData.append('main.js', new Blob([main], { type: 'application/javascript+module' }))
formData.append('metadata.json', new Blob([metadata], { type: 'application/json' }))
return await $fetch(`${baseUrl}/namespaces/timo/scripts/hello`, { method:"PUT", body:formData, headers })

const main = `
export default {
    fetch(request) {
        return new Response('Hello World');
    }
} 
`
const metadata = JSON.stringify({ main_module: "main.js" })
const formData = new FormData();
formData.append('main.js', new Blob([main], { type: 'application/javascript+module' }))
formData.append('metadata.json', new Blob([metadata], { type: 'application/json' }))
return await $fetch(`${baseUrl}/namespaces/timo/scripts/hello`, { method:"PUT", body:formData, headers })

And I keep getting:

"could not read content for part metadata"

"could not read content for part metadata"

"could not read content for part metadata"

"could not read content for part metadata"

Ccosbgn Hey does anyone knows how to upload a script via API? I'm trying: ```js const...

Chaika•3/21/24, 2:58 PM

iirc

formData.append('metadata.json', new Blob([metadata], { type: 'application/json' }))

should be

formData.append('metadata', new Blob([metadata], { type: 'application/json' }))

cosbgnOP•3/21/24, 3:04 PM

Great, using file an metadata it now works:

const formData = new FormData();
formData.append('main', new File([main], 'main.js', { type: 'application/javascript+module' }));
    formData.append('metadata', new File([metadata], 'metadata.json', { type: 'application/json' }));

const formData = new FormData();
formData.append('main', new File([main], 'main.js', { type: 'application/javascript+module' }));
    formData.append('metadata', new File([metadata], 'metadata.json', { type: 'application/json' }));

Thanks a lot

Ttanushree │ Workers PM ❓ Question for this group — would you be interesting in sharing you’ve built or...

cosbgnOP•3/22/24, 5:43 PM

Sent you a DM

Nick Randall•3/27/24, 8:21 PM

Hello! Anybody know if it's possible to CNAME a custom domain to the domain of a worker published to "workers for platforms"? Basically I want to CNAME "www.fancydomain.com" -> "fancyapp.dispatcher.domain.com" where the dispatch worker is tied to *.dispatcher.domain.com/**.dispatcher.domain.com/*

NNick Randall Hello! Anybody know if it's possible to CNAME a custom domain to the domain of a...

DaniFoldi•3/27/24, 8:39 PM

Hey! For something like that I think you'll need to use Custom Hostnames from Cloudflare for SaaS, and have your dispatcher worker respond to

*/*

*/*

routes

rob•4/3/24, 9:00 PM

can you bind KV /d1 etc to a worker via API calls or do you need to use the toml file for that

Rrob can you bind KV /d1 etc to a worker via API calls or do you need to use the toml...

Isaac McFadyen•4/3/24, 11:13 PM

API calls, and in fact for Workers for Platforms (different from regular Workers) that's the only way to bind things to user workers.

Isaac McFadyen•4/3/24, 11:13 PM

For regular Workers you can also do it via API.

Isaac McFadyen•4/3/24, 11:14 PM

Keep in mind in both cases it will result in a redeploy of your Worker so it might take a few seconds to propagate globally/your worker will be reset.

IIsaac McFadyen API calls, and in fact for Workers for Platforms (different from regular Workers...

rob•4/3/24, 11:22 PM

yah its for WfP so i could deploy then bind , i cant deploy with things binded already

rob•4/3/24, 11:22 PM

tanushree │ Workers PM•4/5/24, 2:26 PM

Big WFP announcement today

https://blog.cloudflare.com/browser-rendering-api-ga-rolling-out-cloudflare-snippets-swr-and-bringing-workers-for-platforms-to-our-paygo-plans

TLDR: WFP is coming down to our paid plan on April 16th!

The Cloudflare Blog

Browser Rendering API GA, rolling out Cloudflare Snippets, SWR, and...

Browser Rendering API is now available to all paid Workers customers with improved session management

schmime•4/5/24, 4:31 PM

Hi friends, new to workers for platforms! What is the story on letting users manage secrets for their workers they upload? Like if my user wants to access their own database from their worker what is best practice for managing that? Thank you for the help!

Bryan•4/5/24, 4:48 PM

Very happy to see Workers for Platforms will be available to everyone!

I want to build a multi-tenant service with Workers for Platforms, but I don't know what I should do with the database.

I have two options: One D1 database for all customers and One D1 database for each customer.

For the first option, I think there will be challenges for data security and I think the size will grow over 10GB quickly (since what I want to do is heavy on data).

For the second option, there are two problems. First, each account can only have 5000 D1 databases, and I think I will go over this limit since I will offer a free tier service. I also found it's not easy to dynamically create D1 database and attach it to my worker script. Second, If one day I need to do a database migration, I will have to do the migration for all databases, and it'll definitely not be easy.

Do you have any suggestions for what I should do?

BBryan Very happy to see Workers for Platforms will be available to everyone! I want t...

Unsmart•4/5/24, 5:52 PM

Currently durable objects are the best tenant based db you can use. D1 is still working on exposing easier tenant based structure.

Unsmart•4/5/24, 5:54 PM

and fwiw the database limit on d1 can easily be raised (its also 50k not 5k)

rob•4/5/24, 8:42 PM

How do you assign worker routes to a customer's domain, if they add their domain (we set it via Cloudflare for SaaS ) Can we then add Worker Routes to the custom domain they added

Rrob How do you assign worker routes to a customer's domain, if they add their domain...

Unsmart•4/5/24, 10:32 PM

If you want all customer domains to go to the same worker its pretty easy just gotta add these 3 worker routes (https://dash.cloudflare.com/?to=/:account/:zone/workers):

<zone-name>/*<zone-name>/* Service:

None

None

*.<zone-name>/**.<zone-name>/* Service:

None

None

*/*

*/*

Service: <worker to route to><worker to route to>

Example:

Unsmart•4/5/24, 10:35 PM

If you only want to specify a specific customers domain then you would just enter their domain in the workers routes.

mycustomer.com/*mycustomer.com/* Service: my-worker-for-customermy-worker-for-customer

Note that you can only have like 3,000 worker routes defined iirc

kian•4/6/24, 11:22 PM

The same as Wrangler, you bundle it (i.e with esbuild) before uploading it

Kai•4/7/24, 1:30 PM

Hello, about the pricing for individual scripts, my assumption is the pricing covers storage of the worker code. is this correct?

Kai•4/7/24, 1:32 PM

if that is the case, has the idea of more fine grained pricing for the storage that the workers take been brought up? I'm imagining a pricing model of
x per 1GB instead of x per script.

Unsmart•4/7/24, 4:40 PM

A static cost per script is easier to calculate which is why it’s that way

UUnsmart A static cost per script is easier to calculate which is why it’s that way

Kai•4/8/24, 3:34 AM

yeah makes sense, thanks

Kai•4/8/24, 4:57 AM

~~is the cost per script pro-rated?~~

If i create a user script and delete it after a week does that incur the whole 0.02 charge?

Walshy•4/8/24, 3:05 PM

We 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>wrangler dispatch-namespace secret put <secret-name> (this is more inline with how pages is handling it)

Walshy•4/8/24, 3:06 PM

cc: @tanushree │ Workers PM

rob•4/8/24, 3:18 PM

yeah i was curious on the same, if we can store secrets for a customers worker

Walshy•4/8/24, 5:16 PM

Yeah in the UI we don't let you modify script bindings iirc

Walshy•4/8/24, 5:16 PM

You can use the API but yeah we should add to wrangler for sure

Aalgads Makes sense. So it sounds like I can't currently add secrets to the WfP script ...

Beny•4/10/24, 3:43 AM

You 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

PUT https://api.cloudflare.com/client/v4/accounts/{account_id}/workers/dispatch/namespaces/{namespace}/scripts/{script_name}/secrets
Content-Type: application/json
X-Auth-Key: YOUR-API-KEY

{
  "name": "DB_PASSWORD",
  "text":  "secretPassword123",
  "type": "secret_text"
}

PUT https://api.cloudflare.com/client/v4/accounts/{account_id}/workers/dispatch/namespaces/{namespace}/scripts/{script_name}/secrets
Content-Type: application/json
X-Auth-Key: YOUR-API-KEY

{
  "name": "DB_PASSWORD",
  "text":  "secretPassword123",
  "type": "secret_text"
}

rob•4/10/24, 11:40 AM

What are the list of type For that

Rrob What are the list of type For that

DaniFoldi•4/10/24, 11:43 AM

here'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

rob•4/10/24, 11:47 AM

rob•4/10/24, 6:30 PM

is it stll not advised to do 1 namespace per "customer" ?

Unsmart•4/10/24, 6:32 PM

A 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

rob•4/10/24, 6:35 PM

yah 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?

Rrob yah ive seen mixed , some recommended 1 per customer other ssaying do all on sam...

Payello•4/10/24, 9:06 PM

KV 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).