Hi! Ok just need some quick confirmation, but do I understand correctly that we are unable to map multiple workers to the same domain but on different paths? For example, I have several queue workers that I need to keep separate and I'd like to map to: - cfw.mydomain.com/send-email -> points to my send-email cfw - cfw.mydomain.com/send-text -> points to my send-text cfw I am unable to do that...right? Since they'd run separate snippets of code. Instead I would need to configure the workers like this: - send-email.mydomain.com -> points to my send-email cfw - send-text.mydomain.com -> points to my send-text cfw It would be nice if the first option is possible because I need to pass the URL to a proxy and I'd like to not have to create several proxy rules that are essentially identical except for the upstream url (aka *.mydomain.com) Just wanted to check, thanks!

You shouldn't have any issue doing that with HTTP Routes, under the Worker Routes tab of your zone, you just create the route exactly as is

cfw.mydomain.com/send-email

, select your service, and then repeat for the send-text worker. If you don't have an existing origin for cfw.mydomain.com, you'll need to create a record though to get traffic flowing through Cloudflare and hit your worker. Cloudflare recommends 100:: for Originless setups, that is, create an AAAA record on cfw.mydomain.com, target

100::

, proxied on.

(When you're on the Worker Routes page you may see Forbidden 10007 errors, just ignore them and they won't hurt you, looks like that "bug" is still around)

oh wow - yea I saw the error when I visited that page earlier and thought I was doing something wrong. Also had no clue about that 100:: record. Thanks so much for clarifying - I got this working using routes. Really appreciate it 🙂

any way to avoid putting the raw key value in the wrangler.toml file? (For my current use-case, it's fine, but future ones.. eh 😛 )

anyone ran into this issue before when trying to publish to npm?

error An unexpected error occurred: "https://registry.yarnpkg.com/-/user/org.couchdb.user:aimoda: Auth rate limited".

https://www.githubstatus.com/incidents/t2xwk9mz56f4 might be related

hmm but isn't npm unrelated?

oh

right

it is

yeah thank you, I'm tired and didn't put 2 and 2 together.

lol no worries

hello friends I created a worker with GDindex and I disabled " online player", but I received below banned as this How can I avoid this ban? & how can I fix it?

Not other than some weird string manipulation at CLI

Hey Question: Can I run a function in my Cloudflare Workers service periodically to fetch data from another server, cache data and then in case of specific data from that another server, send a message to connected clients? I want to use WS here.

A Cron Trigger?

Yeah I am looking into this. I'm not much of a JS dev, I only do Dart, so JS stuff, especially server code are strangers to me 😄 I think I need to add a schedule listener, fetch data and cache, then read from that data in my websocket stuff.

Make sure you use the Module syntax(export default, rather than addEventListener), so that you don’t have to upgrade later

Aha, thanks 😄

Is there no way of pausing a worker temporarily, short of deleting all the routes?

Deleting the Worker itself?

lol not really what I would call "pausing"

I mean, if you are using wrangler, it is basically the same, other than the analytics being reset

last I checked you could delete and republish a worker and that stuff would stay

wrangler delete

ez

I'm setting up my first worker service binding. for local dev do I need to have the bound service running with wrangler too?

I tried without and it is

undefined

without

--local

it does work but then my durable objects won't work