A longer explanation is that cloudflare workers are meant to run bits of code and then terminate. A

A longer explanation is that cloudflare workers are meant to run bits of code and then terminate. A discord bot needs to continue running indefinitely.

RRazzmatazz A longer explanation is that cloudflare workers are meant to run bits of code an...

Hello, I’m Allie!•3/30/24, 10:36 AM

Well, that’s not entirely the case. It is more that Discord has blocked Worker’s IPs from connecting to the Gateway

Hello, I’m Allie!•3/30/24, 10:37 AM

You could build a Gateway Bot with Durable Objects. It wouldn’t be quite as ergonomic as one built in Node, but it definitely is doable

Hello, I’m Allie!•3/30/24, 10:37 AM

Other than that it wouldn’t actually connect

HHello, I’m Allie!Well, that’s not entirely the case. It is more that Discord has blocked Worker’s...

RazzmatazzOP•3/30/24, 11:23 AM

Good point. Multiple reasons it’s not possible to use the discord.js package to build a bit in a worker.

RRazzmatazz Good point. Multiple reasons it’s not possible to use the discord.js package to ...

Hanging_on_edge•3/30/24, 12:23 PM

can you please give other reasons too

HHanging_on_edge can you please give other reasons too

RazzmatazzOP•3/30/24, 12:27 PM

How many independently-disqualifying reasons do you need for why it's not feasible to use discord.js to make a discord bot in a worker?

vloe•3/30/24, 1:28 PM

i'm so lost...

vloe•3/30/24, 1:29 PM

added cors to my cf-worker but everybody can still access my endpoint:

vloe•3/30/24, 1:30 PM

#[event(fetch)]
async fn fetch(req: HttpRequest, _env: Env, _ctx: Context) -> Result<Response<Body>> {
    console_error_panic_hook::set_once();

    let cors = CorsLayer::new()
        .allow_origin("https://shorter.dev".parse::<HeaderValue>().unwrap())
        .allow_headers([CONTENT_TYPE])
        .allow_methods([Method::GET, Method::POST, Method::HEAD, Method::OPTIONS]);

    let app = Router::new()
        .route("/", get(|| async { "shorter.dev server!" }))
        .merge(mount())
        .layer(cors)
        .call(req)
        .await?;

    Ok(app)
}

#[event(fetch)]
async fn fetch(req: HttpRequest, _env: Env, _ctx: Context) -> Result<Response<Body>> {
    console_error_panic_hook::set_once();

    let cors = CorsLayer::new()
        .allow_origin("https://shorter.dev".parse::<HeaderValue>().unwrap())
        .allow_headers([CONTENT_TYPE])
        .allow_methods([Method::GET, Method::POST, Method::HEAD, Method::OPTIONS]);

    let app = Router::new()
        .route("/", get(|| async { "shorter.dev server!" }))
        .merge(mount())
        .layer(cors)
        .call(req)
        .await?;

    Ok(app)
}

Vvloe ```rust #[event(fetch)] async fn fetch(req: HttpRequest, _env: Env, _ctx: Contex...

Hello, I’m Allie!•3/30/24, 1:32 PM

CORS does not prevent those that don't respect CORS from hitting your Worker, if that is what you mean

Hello, I’m Allie!•3/30/24, 1:32 PM

It only works for stuff like Browsers

vloe•3/30/24, 1:38 PM

thank you. any idea how i can prevent everyone from hitting my worker except my own requests?

Vvloe thank you. any idea how i can prevent everyone from hitting my worker except my ...

Hello, I’m Allie!•3/30/24, 1:39 PM

You can check certain headers to see if they match, but if the attackers are persistent, there isn't much you can do

Hello, I’m Allie!•3/30/24, 1:40 PM

There isn't a 100% foolproof way to ensure that a request is only coming from your app(unless you control the client, and don't allow anyone access to it)

vloe•3/30/24, 1:46 PM

i see, thank you!

Ashley•3/30/24, 1:53 PM

Is there a knack to getting service bindings working locally? I have two running locally, both using

npm run dev

npm run dev

and worker A is bound to worker B. Worker B calls Worker A, and when I start Worker B I get:

⛅️ wrangler 3.41.0
-------------------
▲ [WARNING] This worker is bound to live services: AUTH (authentication-worker)


Your worker has access to the following bindings:
- Services:
  - AUTH: authentication-worker
▲ [WARNING] ⎔ Support for service bindings in local mode is experimental and may change.

⛅️ wrangler 3.41.0
-------------------
▲ [WARNING] This worker is bound to live services: AUTH (authentication-worker)


Your worker has access to the following bindings:
- Services:
  - AUTH: authentication-worker
▲ [WARNING] ⎔ Support for service bindings in local mode is experimental and may change.

The warning itself is a little confusing, as it's running locally, so I don't know why it's mentioning live. Either way, when I hit it with a request, I get

Cannot read properties of undefined (reading 'fetch')

Cannot read properties of undefined (reading 'fetch')

if I run Worker B in remote mode, it works fine (but presumably hits my live worker), so I'm quite confused. Any ideas?

Ashley•3/30/24, 1:53 PM

(both are using the same version of Wrangler)

RRazzmatazz How many independently-disqualifying reasons do you need for why it's not feasib...

Hanging_on_edge•3/30/24, 2:06 PM

Sorry I couldnt understand thats why

AAshley Is there a knack to getting service bindings working locally? I have two running...

Ashley•3/30/24, 2:10 PM

Okay I just read https://github.com/cloudflare/workers-sdk/issues/1182, in which case https://developers.cloudflare.com/workers/configuration/bindings/about-service-bindings/#local-development is highly misleading

Cretezy•3/30/24, 3:32 PM

Is it possible to see the cron logs when an error happens?

CCretezy Is it possible to see the cron logs when an error happens?

Hello, I’m Allie!•3/30/24, 3:33 PM

Only if you have a tail session/logpush job running

Cretezy•3/30/24, 3:44 PM

Alright thanks. I think capturing the error message when an exception is thrown inside a cron worker and displaying it inside the log cron triggers would be very useful.

CCretezy Alright thanks. I think capturing the error message when an exception is thrown ...

Hello, I’m Allie!•3/30/24, 3:46 PM

It should show up in the dash tail thing, if that is what you mean

Cretezy•3/30/24, 3:47 PM

Yeah I will do that for the next run, but it's hard to tail at 3am when my cron is running

CCretezy Yeah I will do that for the next run, but it's hard to tail at 3am when my cron ...

Hello, I’m Allie!•3/30/24, 3:47 PM

Logpush is free for Workers events, so that should be usable too

Cretezy•3/30/24, 3:48 PM

Ah okay, going to check that out. Thank you!

Original message was deleted

Hello, I’m Allie!•3/30/24, 3:49 PM

Or well, free with Workers Paid

Hello, I’m Allie!•3/30/24, 3:49 PM

I guess

Cretezy•3/30/24, 3:50 PM

Yeah, I don't see Logs under "Analytics & Logs"

Cretezy•3/30/24, 3:51 PM

I will just

wrangler tail

wrangler tail

overnight and hope for the best

Cretezy•3/30/24, 3:51 PM

while true; do wrangler tail; end

while true; do wrangler tail; end

CCretezy Ah okay, going to check that out. Thank you!

Hello, I’m Allie!•3/30/24, 3:51 PM

You could also run a manual trigger?

Cretezy•3/30/24, 3:52 PM

How can I manually trigger a production cron?

Cretezy•3/30/24, 3:53 PM

I guess. It's a very simple Worker so I don't want to add too much to it. Tailing will do the job for now. Otherwise I'll move the code in a route and test it that way

johtso•3/30/24, 4:12 PM

any thoughts on what the best option is currently for observation (debugging) when using workers / DOs? sentry? honeycomb? small project so generous free tier of honeycomb had me interested

varlakshmiwhale•3/30/24, 5:24 PM

i am unable to login the wesite which i was using in my odl laptop to new laptop..plz help me

HHello, I’m Allie!Only if you have a tail session/logpush job running

bun•3/30/24, 5:59 PM

Logpush is only for enterprise?

Bbun Logpush is only for enterprise?

DaniFoldi•3/30/24, 6:15 PM

Logpush has a Workers dataset, which is available on paid plans, no ent needed

bun•3/30/24, 8:27 PM

Why doesnt it work with axiom then? It gave me an error that it required an enterprise plan @Blob | Rollback

Bbun Why doesnt it work with axiom then? It gave me an error that it required an ente...

DaniFoldi•3/30/24, 8:28 PM

You mean Axiom gave you the error?

bun•3/30/24, 8:28 PM

Yes

DaniFoldi•3/30/24, 8:29 PM

Interesting, that should probably be brought up with them

DaniFoldi•3/30/24, 8:30 PM

They also have a discord server, and @luna can hopefully help you out (I hope you don’t mind the ping :MeowHeartCloudflare: )

bun•3/30/24, 9:33 PM

Even in the docs they mention you need an enterprise account unfortunately even though i have workers datasets available

Jorge•3/30/24, 9:58 PM

I was wondering if anyone is building more than 1 project on the same cloudflare account. Like imagine you are a indie hacker, and you are building a couple of projects, do you need a cloudflare account for each different project?

JJorge I was wondering if anyone is building more than 1 project on the same cloudflare...

Hello, I’m Allie!•3/30/24, 10:00 PM

It depends. You can definitely have many projects on your account. But, if you want to turn it into a business, I would probably put it on its own account

Hello, I’m Allie!•3/30/24, 10:00 PM

Especially if you are working for a client

HHello, I’m Allie!It depends. You can definitely have many projects on your account. But, if you w...

Jorge•3/30/24, 10:03 PM

yeah, you just gave me the confirmation I was needing, I think it would be impossible to transfer the workers, d1, r2's to a different account afterwards... thank you so much for your sonic response

JJorge yeah, you just gave me the confirmation I was needing, I think it would be impos...

Hello, I’m Allie!•3/30/24, 10:05 PM

Not quite on that part. While it can be difficult, and may not have a prebuilt solution, it definitely isn't impossible to move stuff between accounts

Hello, I’m Allie!•3/30/24, 10:05 PM

Though I would generally start on the account I want to stay on, if at all possible

#[event(fetch)] async fn fetch(req: HttpRequest, _env: Env, _ctx: Context) -> Result<Response<Body>> { console_error_panic_hook::set_once(); let cors = CorsLayer::new() .allow_origin("https://shorter.dev".parse::<HeaderValue>().unwrap()) .allow_headers([CONTENT_TYPE]) .allow_methods([Method::GET, Method::POST, Method::HEAD, Method::OPTIONS]); let app = Router::new() .route("/", get(|| async { "shorter.dev server!" })) .merge(mount()) .layer(cors) .call(req) .await?; Ok(app) }

⛅️ wrangler 3.41.0 ------------------- ▲ [WARNING] This worker is bound to live services: AUTH (authentication-worker) Your worker has access to the following bindings: - Services: - AUTH: authentication-worker ▲ [WARNING] ⎔ Support for service bindings in local mode is experimental and may change.

A longer explanation is that cloudflare workers are meant to run bits of code and then terminate. A

Similar Threads

Similar Threads

Similar Threads