since assets are not yet available in workers for platforms, what's the easiest workaround for now?

since assets are not yet available in workers for platforms, what's the easiest workaround for now? https://developers.cloudflare.com/workers/static-assets/ Want to deploy custom react apps

Cloudflare Docs

Static Assets | Cloudflare Workers docs

Create full-stack applications deployed to Cloudflare Workers.

WWalshy yep you can rpc to a user worker

nclevenger•11/11/24, 12:30 PM

Is there an example of using RPC with dynamic dispatch?

Tal•11/11/24, 7:14 PM

Can you use durable objects on workers for platforms? Can user workers and dynamic dispatch workers both access them?

TTal Can you use durable objects on workers for platforms? Can user workers and dynam...

skorfmannOP•11/11/24, 7:48 PM

Was wondering that as well. The docs are stating any bindings would work, but not sure if just from the main account or from user namespaces as well, I.e. deployed / created on behalf of the user

Sskorfmann since assets are not yet available in workers for platforms, what's the easiest ...

skorfmannOP•11/11/24, 9:05 PM

ok, I think that's probably the answer https://developers.cloudflare.com/kv/examples/workers-kv-to-serve-assets/

Cloudflare Docs

Store and retrieve static assets with Workers KV | Cloudflare Worke...

Example of how to use Workers KV to store static assets

TTal Can you use durable objects on workers for platforms? Can user workers and dynam...

Payello•11/12/24, 4:18 PM

Yes you can. User workers can host DOs, and access their own DOs or DOs from account-level workers. Accessing other user workers DOs is either unsupported or not documented.
To solve that limitation in our setup we use a 2nd user worker that hosts all the DOs, and do some magic with service bindings so the original user worker, our dispatcher and other user scripts can access them.

157267•11/13/24, 11:27 AM

const client = new Cloudflare({
apiToken: process.env["CLOUDFLARE_API_TOKEN"],
});

const zones = await client.zones.list();

console.log(zones);

Peps•11/13/24, 11:58 AM

dash is always kinda sluggish

Peps•11/13/24, 11:58 AM

but I haven't noticed any issues specifically with CF Workers

Peps•11/13/24, 11:59 AM

are you noticing it specifically with Workers for Platforms?

Bbanyan ah sorry, I didn't understand Workers for Platforms, maybe the channel is not ap...

boop•11/13/24, 12:35 PM

#workers-discussions is probably a better bet

Bbanyan does anyone feel cloudflare workers seems to be slow? even I feel like dash.clou...

Robin Lindner•11/13/24, 7:58 PM

For me radar.cloudflare.com is very often slow, but that might be also some peering things with the Deutsche Telekom (german ISP)

Ryan Djurovich•11/15/24, 1:29 AM

Are Workers Builds coming to Workers for Platforms? For my use case this would be helpful

PPayello Yes you can. User workers can host DOs, and access their own DOs or DOs from acc...

Tal•11/16/24, 11:50 PM

Where is this documented?

TTal Where is this documented?

Payello•11/17/24, 12:12 AM

It's the exact same as regular workers

javeed•11/19/24, 10:52 AM

Hi guys,

I have proxied the workers custom domain with the https://flexiff.saurabhbhatnagar.in/8zypxuri domain, if i published new content in the page, cache was not cleared suddenly, it is taking 4 hours default cloudflare cache.

https://flexiff.saurabhbhatnagar.in this domain

test

FlexiFunnels

javeed•11/19/24, 10:53 AM

may i know how to clear the cache in the worker?

amlcodes•11/23/24, 1:50 AM

major blocker on static assets for now, eagerly waiting

any workaround? (trying to take advantage of frameworks on workers :D)

Aamlcodes major blocker on static assets for now, eagerly waiting ❤️ any workaround? (tryi...

Payello•11/24/24, 2:04 PM

You could develop your own assets fetcher using KV or R2, but it's not the same unfortunately

spider•11/24/24, 10:39 PM

Is there an updated doc for the limitations on WFP? What features are limited or not available in user workers (Durable Objects, Workflow, queues, etc)?

Chadi•11/26/24, 7:07 AM

good morinng

Chadi•11/26/24, 7:07 AM

morning !!

dmaretskyi•12/4/24, 4:16 PM

Hello, we're building a functions runtime on top of workers-for-platforms. We've built an API that allows users to deploy a function script, and then execute it either by an HTTP call, or based on a trigger like a cron job or a database mutation.

Currently we're struggling with testing this system. As far as I know there's no way to deploy a worker to a dispatch-namespace locally.

Any suggestions from the Cloudflare team on how to test dispatch-namespaces locally would be appreciated.

Ddmaretskyi Hello, we're building a functions runtime on top of workers-for-platforms. We've...

Mykola•12/6/24, 3:31 PM

Ddmaretskyi Hello, we're building a functions runtime on top of workers-for-platforms. We've...

dmaretskyi•12/6/24, 3:33 PM

@tanushree │ Workers PM We'd love to connect with someone from the workers-for-platforms team to share feedback and ask some questions about the product.

PizzaConsole•12/6/24, 9:33 PM

question, here, is there a way to do a spend cap, example like number of requests received?

https://developers.cloudflare.com/cloudflare-for-platforms/workers-for-platforms/configuration/custom-limits/

Cloudflare Docs

Custom limits · Cloudflare for Platforms docs

Custom limits allow you to programmatically enforce limits on your customers' Workers' resource usage. You can set limits for the maximum CPU time and number of subrequests per invocation. If a user Worker hits either of these limits, the user Worker will immediately throw an exception.

Sadath•12/9/24, 2:04 PM

Hi team , just hopped around cloudfare workers wondering , if there is a way to deploy my own models into workers ai that huggingface do not support direct deployment to workers ai currently . And if I wanted to re-train that model privately on my data what would the process look like

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

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

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?

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?

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

Yes it is

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

Excellent! Good to know, thanks

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"

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.

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

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

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!

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

Nvm, I'm just misusing dispatch namespaces

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

Why it is written in documentation: We discourage creating a new namespace for each customerWe discourage creating a new namespace for each customer?

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

Because 1 namespace can handle infinite scripts

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

but you need 1 binding per namespace

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

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

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

Cause they need to be set in wrangler.toml?

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

Yes, you need a binding per namespace

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?

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

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

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

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

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

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

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

since assets are not yet available in workers for platforms, what's the easiest workaround for now?

Similar Threads

Similar Threads

Similar Threads