Hi team , just hopped around cloudfare workers wondering , if there is a way to deploy my own models

SSadath Hi team , just hopped around cloudfare workers wondering , if there is a way to ...

1

1984 Ford Laser•12/14/24, 8:46 AM

No

P

Predo•12/16/24, 5:40 PM

Hi everyone. I started to use the workers-for-plataforms today and I'm having some trouble regarding env variables.

My dispatcher does see all my enviroment variables, but my worker that is in the same namespace does not recieve any variables in the "env" parameter of the fetch function. Does any one know how to fix that?

S

scruffy•12/16/24, 6:12 PM

I know it's not available right now, but does anyone know whether Workers Static Assets is on the roadmap for WFP?

W

Walshy•12/16/24, 6:34 PM

Yes it is

S

scruffy•12/17/24, 5:52 AM

Excellent! Good to know, thanks

M

Mykola•12/17/24, 6:37 PM

Hello guys, I am working on a project with dynamically uploaded user workers, and I am trying to write unit test that works locally with

DISPATCH_NAMESPACE

DISPATCH_NAMESPACE

binding.
I am using wrangler version

0.0.0-2ca4eaef5

0.0.0-2ca4eaef5

with tag

dispatch-namespaces-dev

dispatch-namespaces-dev

as recommended in

workers for platforms

workers for platforms

documentation.
Test scenario is inspired by https://developers.cloudflare.com/cloudflare-for-platforms/workers-for-platforms/get-started/developing-with-wrangler/ and looks like that:
0) Start

unstable_dev

unstable_dev

"outbound worker".
1) Start

unstable_dev

unstable_dev

"dispatch worker" that has

DISPATCH_NAMESPACE

DISPATCH_NAMESPACE

binding with

outbound = { service = "outbound-worker" }

outbound = { service = "outbound-worker" }

2) "Dispatch worker" makes

PUT

PUT

request <ACCOUNT_ID>/workers/dispatch/namespaces/<NAMESPACE>/scripts/<SCRIPT_NAME> to my local nodejs sever that spawns child process with

wrangler dev

wrangler dev

with user code passed in request body (I am doing it for local testing only, in production it will be pointed to https://api.cloudflare.com).
Example of user worker's config:

name = "0193d5cc-506a-77db-a12a-c81bd1d6b6dc-0-0-0"
main = "./bootloader.js"
compatibility_date = "2024-04-05"
compatibility_flags = [ "nodejs_compat" ]
dispatch_namespace = "dev-functions"

name = "0193d5cc-506a-77db-a12a-c81bd1d6b6dc-0-0-0"
main = "./bootloader.js"
compatibility_date = "2024-04-05"
compatibility_flags = [ "nodejs_compat" ]
dispatch_namespace = "dev-functions"

name = "0193d5cc-506a-77db-a12a-c81bd1d6b6dc-0-0-0"
main = "./bootloader.js"
compatibility_date = "2024-04-05"
compatibility_flags = [ "nodejs_compat" ]
dispatch_namespace = "dev-functions"

name = "0193d5cc-506a-77db-a12a-c81bd1d6b6dc-0-0-0"
main = "./bootloader.js"
compatibility_date = "2024-04-05"
compatibility_flags = [ "nodejs_compat" ]
dispatch_namespace = "dev-functions"

3) After mocked upload, "dispatch worker" is doing

const worker = DISPATCH_NAMESPACE.get(<SCRIPT_NAME>); worker.fetch(...)

const worker = DISPATCH_NAMESPACE.get(<SCRIPT_NAME>); worker.fetch(...)

to dispatch user worker.
On this step I am getting error response

[wrangler] Couldn\'t find 'wrangler dev' session for "0193d5cc-506a-77db-a12a-c81bd1d6b6dc-0-0-0" in namespace "dev-functions" to proxy to

[wrangler] Couldn\'t find 'wrangler dev' session for "0193d5cc-506a-77db-a12a-c81bd1d6b6dc-0-0-0" in namespace "dev-functions" to proxy to

. And no request is being intercepted by my outbound worker.

So I do not understand why my mocked

user workers

user workers

is not being seen by dispatch worker, maybe I should not be using

unstable_dev

unstable_dev

for starting dispatch worker. Would appreciate any help, thanks in advance.

Cloudflare Docs

Local development · Cloudflare for Platforms docs

To test your Dispatch Worker, user Worker and Outbound Worker before deploying to production, you can use Wrangler for development and testing.

M

Mykola•12/17/24, 6:39 PM

cc @Walshy Nice to meet you, just trying to get someone's attention here

M

Mathis @ blaxel.ai•12/19/24, 10:40 AM

Hi everyone!

I'm testing out Workers for my platform and currently building a dispatch worker with dynamic namespace bindings that are added or removed via API. However, I have a question about managing namespace bindings during deployment.

In my CI/CD setup for the dispatch worker, I have a wrangler.toml file, but I don’t want it to override the dynamic namespace bindings created through the API.

Is there a way to handle this using Wrangler? Or should I rely solely on the API for this scenario? Any advice would be greatly appreciated!

M

Mathis @ blaxel.ai•12/19/24, 5:30 PM

Nvm, I'm just misusing dispatch namespaces

M

Mathis @ blaxel.ai•12/19/24, 7:29 PM

Why it is written in documentation:

We discourage creating a new namespace for each customer

We discourage creating a new namespace for each customer

?

W

Walshy•12/19/24, 7:34 PM

Because 1 namespace can handle infinite scripts

W

Walshy•12/19/24, 7:34 PM

but you need 1 binding per namespace

W

Walshy•12/19/24, 7:34 PM

It provides no benefit security or otherwise but massively impacts dx on your side

M

Mathis @ blaxel.ai•12/19/24, 7:35 PM

Cause they need to be set in wrangler.toml?

W

Walshy•12/19/24, 7:36 PM

Yes, you need a binding per namespace

M

Mathis @ blaxel.ai•12/19/24, 7:37 PM

Can't I use API to abstract this constraint, just pushing the script instead of the whole bundle?

W

Walshy•12/19/24, 7:37 PM

Nope, I'm not sure how you'd go about doing that

M

Mathis @ blaxel.ai•12/19/24, 7:39 PM

So updating my code will need me to update dynamically my bindings after?

W

Walshy•12/19/24, 7:44 PM

Let's step back - why do you want a namespace per customer?

M

Mathis @ blaxel.ai•12/19/24, 7:47 PM

It's easier to manage customers like this instead based on tags, it'll be quicker to develop our backend

D

Dmitry•12/21/24, 4:00 PM

What's the latency look like with WFP compared to Service Bindings?

D

Dmitry•12/21/24, 4:01 PM

I know the Service Bindings docs say no added latency... curious how WFP differs

W

Walshy•12/21/24, 6:10 PM

Same deal

D

Dmitry•12/28/24, 5:36 AM

Hey so I'm building a sort of API gateway for my project using Workers for Platforms. I might have done something weird... and now i'm getting errors on the dashboard lol. So I basically attached the 'dispatcher' binding to multiple 'user' workers. My reasoning behind this is because i'd like user workers to be able to make RPC calls to other user workers. When I say user workers... they won't actually be user facing (you can think more of them being different Services). Obv binding the dispatch workers to user workers normally would not be a good idea. Can someone take a look at my account? It says "Unknown Error" occured in a red box when I try to load the page

D

Dmitry•12/28/24, 5:37 AM

It does work tho... which is cool... I can basically RPC from any user worker back to my dispatcher reach to another user worker (Service)

D

Dmitry•12/28/24, 5:42 AM

For example i'll have a service (user worker) specifically with auth related endpoints (Hono API). If I have a different hello world service for example... I can bind the dispatch worker (basically my gateway) to it and do an auth check via RPC to that auth service.

D

Dmitry•12/28/24, 5:43 AM

But I don't think the dashboard likes the fact that I binded dispatch workers to my user workers :kekw:

D

Dmitry•12/28/24, 5:47 AM

And it says "There are no Workers bound to this namespace" now

D

Dmitry•12/28/24, 10:03 PM

Anyone have an example of doing RPC with WFP Dispatch Namespaces?

D

Dmitry•12/28/24, 10:56 PM

Here's what I tried..

import { WorkerEntrypoint } from 'cloudflare:workers'

declare class MyEntrypointType extends WorkerEntrypoint {
  sum(args: number[]): number
}

interface Env {
  DISPATCHER: DispatchNamespace
}

export default {
  async fetch(req, env, ctx): Promise<Response> {
    const worker = env.DISPATCHER.get(
      'customer-worker-2'
    ) as Service<MyEntrypointType>
    const sum = await worker.sum([1, 2, 3])
    return new Response(`${sum}`)
  }
} satisfies ExportedHandler<Env>

import { WorkerEntrypoint } from 'cloudflare:workers'

declare class MyEntrypointType extends WorkerEntrypoint {
  sum(args: number[]): number
}

interface Env {
  DISPATCHER: DispatchNamespace
}

export default {
  async fetch(req, env, ctx): Promise<Response> {
    const worker = env.DISPATCHER.get(
      'customer-worker-2'
    ) as Service<MyEntrypointType>
    const sum = await worker.sum([1, 2, 3])
    return new Response(`${sum}`)
  }
} satisfies ExportedHandler<Env>

import { WorkerEntrypoint } from 'cloudflare:workers'

declare class MyEntrypointType extends WorkerEntrypoint {
  sum(args: number[]): number
}

interface Env {
  DISPATCHER: DispatchNamespace
}

export default {
  async fetch(req, env, ctx): Promise<Response> {
    const worker = env.DISPATCHER.get(
      'customer-worker-2'
    ) as Service<MyEntrypointType>
    const sum = await worker.sum([1, 2, 3])
    return new Response(`${sum}`)
  }
} satisfies ExportedHandler<Env>

import { WorkerEntrypoint } from 'cloudflare:workers'

declare class MyEntrypointType extends WorkerEntrypoint {
  sum(args: number[]): number
}

interface Env {
  DISPATCHER: DispatchNamespace
}

export default {
  async fetch(req, env, ctx): Promise<Response> {
    const worker = env.DISPATCHER.get(
      'customer-worker-2'
    ) as Service<MyEntrypointType>
    const sum = await worker.sum([1, 2, 3])
    return new Response(`${sum}`)
  }
} satisfies ExportedHandler<Env>

import { WorkerEntrypoint } from 'cloudflare:workers'

export default {
  async fetch(
    request: Request,
    env: Env,
    ctx: ExecutionContext
  ): Promise<Response> {
    throw new Error(
      "Worker only used for RPC calls, there's no default fetch handler"
    )
  }
}

export class SumEntrypoint extends WorkerEntrypoint {
  sum(args: number[]): number {
    return args.reduce((a, b) => a + b)
  }
}

import { WorkerEntrypoint } from 'cloudflare:workers'

export default {
  async fetch(
    request: Request,
    env: Env,
    ctx: ExecutionContext
  ): Promise<Response> {
    throw new Error(
      "Worker only used for RPC calls, there's no default fetch handler"
    )
  }
}

export class SumEntrypoint extends WorkerEntrypoint {
  sum(args: number[]): number {
    return args.reduce((a, b) => a + b)
  }
}

import { WorkerEntrypoint } from 'cloudflare:workers'

export default {
  async fetch(
    request: Request,
    env: Env,
    ctx: ExecutionContext
  ): Promise<Response> {
    throw new Error(
      "Worker only used for RPC calls, there's no default fetch handler"
    )
  }
}

export class SumEntrypoint extends WorkerEntrypoint {
  sum(args: number[]): number {
    return args.reduce((a, b) => a + b)
  }
}

import { WorkerEntrypoint } from 'cloudflare:workers'

export default {
  async fetch(
    request: Request,
    env: Env,
    ctx: ExecutionContext
  ): Promise<Response> {
    throw new Error(
      "Worker only used for RPC calls, there's no default fetch handler"
    )
  }
}

export class SumEntrypoint extends WorkerEntrypoint {
  sum(args: number[]): number {
    return args.reduce((a, b) => a + b)
  }
}

But I get an error

The RPC receiver does not implement the method "sum".

The RPC receiver does not implement the method "sum".

when I try to use it

D

Dmitry•12/29/24, 12:19 AM

this worked!!

import { WorkerEntrypoint } from 'cloudflare:workers'

export default class extends WorkerEntrypoint {
  async fetch() {
    return new Response('Hello from User Worker')
  }

  sum(args: number[]): number {
    return args.reduce((a, b) => a + b)
  }
}

import { WorkerEntrypoint } from 'cloudflare:workers'

export default class extends WorkerEntrypoint {
  async fetch() {
    return new Response('Hello from User Worker')
  }

  sum(args: number[]): number {
    return args.reduce((a, b) => a + b)
  }
}

import { WorkerEntrypoint } from 'cloudflare:workers'

export default class extends WorkerEntrypoint {
  async fetch() {
    return new Response('Hello from User Worker')
  }

  sum(args: number[]): number {
    return args.reduce((a, b) => a + b)
  }
}

import { WorkerEntrypoint } from 'cloudflare:workers'

export default class extends WorkerEntrypoint {
  async fetch() {
    return new Response('Hello from User Worker')
  }

  sum(args: number[]): number {
    return args.reduce((a, b) => a + b)
  }
}

D

Dmitry•12/29/24, 12:19 AM

Thanks so much @Skye

B

ByteBeast•12/30/24, 2:52 AM

Hi guys, Could anyone please help me with cloudflare worker and websocket.

I want to connect deepgram socket in CF worker but getting same error
Error: "Failed to establish WebSocket connection: Error: ws does not work in the browser. Browser clients must use the native WebSocket object"

P

pravin•1/2/25, 3:33 AM

Hey folks, thinking about using CF Workers For Platform to build an Integrations Platform, and I was wondering if it's suitable for processing webhook events where the User worker processing the event might be slow? From my reading of the product document, it appears to be more suited for processing sync requests?

Ppravin Hey folks, thinking about using CF Workers For Platform to build an Integrations...

R

rdutton•1/7/25, 2:31 AM

One of the challenges with webhooks is sending a response within the required timeframe. e.g. Shopify and Xero will only wait 5 seconds. Assuming your application processing could take longer that 5 seconds, two options are: 1) Respond early and continue execution using 'waitUntil'. see https://developers.cloudflare.com/workers/runtime-apis/context/#waituntil or 2) Grab the request data (optionally store it) and send it into a queue for later processing by another worker, then respond. Personally I use the second pattern as it provides more visibility and the opportunity to replay the webhook event if needed.

Rrdutton One of the challenges with webhooks is sending a response within the required ti...

P

pravin•1/7/25, 5:31 AM

Yep, makes sense, thanks @rdutton

I didn't see Queues in the WfP documentation. I suppose everything that works with Workers will also work in a WfP setting?

Ppravin Yep, makes sense, thanks @rdutton I didn't see Queues in the WfP documentation...

R

rdutton•1/7/25, 5:37 AM

I haven't used WFP before so can't say for sure. Someone else might be able to confirm.

C

christianklotz•1/8/25, 2:02 PM

I followed the guide which uses

wranger@dispatch-namespaces-dev

wranger@dispatch-namespaces-dev

but local dev environment fails with

[wrangler] Couldn't find `wrangler dev` session for "customer-worker-1" in namespace "workers-for-platforms-playground" to proxy to

[wrangler] Couldn't find `wrangler dev` session for "customer-worker-1" in namespace "workers-for-platforms-playground" to proxy to

Can someone confirm that this is actually supported in this wrangler dev branch release? Or is uploading scripts the only way to debug WFP apps?

S

sherlock•1/9/25, 6:22 AM

I added a custom domain and when I access it through the custom domain, I get this error

error code: 1003

S

sherlock•1/9/25, 6:24 AM

help me

A

arun2728•1/9/25, 7:59 AM

I am getting this error when creating a new cloudflare worker - workers.api.error.exceeded_allowed_number_of_scripts. When I checked the cloudflare docs it suggested to upgrade to Cloudflare Workers for Platforms. And I upgraded the plan. But I am still getting this error. Can anyone help me with it?

W

Walshy•1/9/25, 1:49 PM

Workers for Platforms is indeed the solution, you'll want to switch to uploading the scripts as Workers for Platforms scripts rather than regular Workers

W

Walshy•1/9/25, 1:50 PM

https://developers.cloudflare.com/api/resources/workers_for_platforms/subresources/dispatch/subresources/namespaces/subresources/scripts/methods/update/

W

Walshy•1/9/25, 5:07 PM

For #1 you should follow the same as #2, add them to ssl for saas and add a CNAME to your main zone

W

Walshy•1/9/25, 5:08 PM

And yeah, for you it seems you can just keep using 1 worker, let it get invoked by ssl for saas and it'll be handled for all customers with ease

W

Walshy•1/9/25, 5:19 PM

I don't think there is a limit on hostnames?

Hi team , just hopped around cloudfare workers wondering , if there is a way to deploy my own models

Similar Threads

Similar Threads

Similar Threads