Reason why I never would use Workers because such limits are the biggest shiq someone can do. Its al

Reason why I never would use Workers because such limits are the biggest shiq someone can do. Its also saying "Yes we have DDoS Protection, but nobody is able anymore to access the Website because the limit was reached :BL_Shrug:

KasumiOP•2/26/24, 7:34 AM

You want to take down a Website? Just get some dudes that are spamming the reload button

KKasumi Reason why I never would use Workers because such limits are the biggest shiq so...

Hello, I’m Allie!•2/26/24, 7:34 AM

I’m not sure I understand? That limit is only on free-plan Workers

KasumiOP•2/26/24, 7:35 AM

And on pro there are no limits?

KKasumi And on pro there are no limits?

Hello, I’m Allie!•2/26/24, 7:35 AM

None that you can’t pay your way out of

Hello, I’m Allie!•2/26/24, 7:35 AM

Wait

DepstR•2/26/24, 7:35 AM

Since when were the fields "Service" and "Protocol" removed in the SRV DNS record?

Hello, I’m Allie!•2/26/24, 7:35 AM

Paying for Pro on a Zone doesn’t affect the amount of Workers requests that you can make

Hello, I’m Allie!•2/26/24, 7:36 AM

Workers Paid and Pro are two separate things

KasumiOP•2/26/24, 7:36 AM

I already paid for CF Pro so I dont pay for Workers too

KKasumi I already paid for CF Pro so I dont pay for Workers too

Hello, I’m Allie!•2/26/24, 7:36 AM

That’s the ticket then

Hello, I’m Allie!•2/26/24, 7:37 AM

You can use millions of Workers Requests on a Free Zone, as long as you pay for Workers Paid

HHello, I’m Allie!That’s the ticket then

KasumiOP•2/26/24, 7:37 AM

Cloudflare would never give discount to a private person

KKasumi Cloudflare would never give discount to a private person

Hello, I’m Allie!•2/26/24, 7:37 AM

Wdym?

Hello, I’m Allie!•2/26/24, 7:37 AM

Hello, I’m Allie!•2/26/24, 7:38 AM

“That’s the ticket” is an expression, meaning that’s the problem

Hello, I’m Allie!•2/26/24, 7:38 AM

It’s not referring to a support/billing ticket

HHello, I’m Allie!You can use millions of Workers Requests on a Free Zone, as long as you pay for ...

KasumiOP•2/26/24, 7:39 AM

Ah okay. But still there are also the limitation that its only possible to use specific node packages. So no fastify and other things

HHello, I’m Allie!It’s not referring to a support/billing ticket

KasumiOP•2/26/24, 7:39 AM

ah okya

KKasumi Ah okay. But still there are also the limitation that its only possible to use s...

Hello, I’m Allie!•2/26/24, 7:40 AM

I mean yeah. But, support for certain Node packages is getting better, it is a limit that applies to everyone, and is pretty well documented, at least in my opinion

Hello, I’m Allie!•2/26/24, 7:40 AM

While Workers is a JS-platform, it isn’t a Node Platform

KasumiOP•2/26/24, 7:41 AM

yes

Vero•2/26/24, 10:48 AM

yep :/

Erisa•2/26/24, 12:49 PM

Please don't ping reply to messages from months ago

KasumiOP•2/26/24, 2:31 PM

#cloudflare-status :lunyWooCAP:

ivxenog•2/26/24, 3:23 PM

unable to see errors in the worker with wrangler tail. Any web interface to see tail logs?

Walshy•2/26/24, 3:44 PM

is your Worker name correct?

WWalshy is your Worker name correct?

ivxenog•2/26/24, 3:44 PM

not sure, I am trying this for the first time. mhl-dev is pages project

Walshy•2/26/24, 3:45 PM

but yeah, you can view in the UI here:

Walshy•2/26/24, 3:45 PM

ah Pages project

Walshy•2/26/24, 3:45 PM

so you will want to do

wrangler pages deployment tail

wrangler pages deployment tail

WWalshy so you will want to do `wrangler pages deployment tail`

ivxenog•2/26/24, 3:46 PM

Okay, trying. It didn't fail at deployment though

Walshy•2/26/24, 3:46 PM

or you can tail here in the UI: https://dash.cloudflare.com/?to=/:account/pages/view/:pages-project/:pages-deployment/functions

Walshy•2/26/24, 3:46 PM

@James i legit need deeplinks for Workers...

WWalshy @James i legit need deeplinks for Workers...

James•2/26/24, 3:48 PM

do it

WWalshy or you can tail here in the UI: https://dash.cloudflare.com/?to=/:account/pages/...

ivxenog•2/26/24, 3:49 PM

ah yes,

pages deployment tail

pages deployment tail

worked. Thank you

WWalshy so you will want to do `wrangler pages deployment tail`

ivxenog•2/26/24, 4:13 PM

Failing for

npx wrangler pages deployment tail

npx wrangler pages deployment tail

as well now after working for many deployments. Getting the

  workers.api.error.script_not_found [code: 8000068]

  workers.api.error.script_not_found [code: 8000068]

this time.

Walshy•2/26/24, 4:13 PM

that should only throw if there's no Function uploaded

WWalshy that should only throw if there's no Function uploaded

ivxenog•2/26/24, 4:18 PM

ah yes. Got the error in deployment logs. But I have another question. I am following https://developers.cloudflare.com/workers/runtime-apis/request/ and here, it says to export default. I am doing it like

export default {
    async fetch(request, env, ctx) { 
        return handleRequest(request, ctx);
    },
};

export default {
    async fetch(request, env, ctx) { 
        return handleRequest(request, ctx);
    },
};

This throws the error

✘ [ERROR] No routes found when building Functions directory: /opt/buildhome/repo/functions

✘ [ERROR] No routes found when building Functions directory: /opt/buildhome/repo/functions

But if I use

export const onRequest = handleRequest

export const onRequest = handleRequest

instead, it worked fine before. I basically need context in my functions to access the bindings name for D1.

ivxenog•2/26/24, 4:21 PM

ah never mind, I think I got it. Context contains request

Walshy•2/26/24, 4:23 PM

https://developers.cloudflare.com/pages/functions/#functions

Cloudflare Docs

Functions · Cloudflare Pages docs

The Cloudflare documentation team is running a survey to measure the effectiveness of the Pages documentation. If you use the Pages documentation to …