I guess another approach would be querying D1 via the REST API (https://developers.cloudflare.com/ap

I guess another approach would be querying D1 via the REST API (https://developers.cloudflare.com/api/operations/cloudflare-d1-raw-database-query).

Bbrighter I guess another approach would be querying D1 via the REST API (https://develope...

Hello, I’m Allie!•7/7/24, 7:50 PM

Yes, though note that this can be much slower

brighterOP•7/7/24, 7:50 PM

That's what I was afraid of.

brighterOP•7/7/24, 7:52 PM

I really don't want to create a worker-d1 pair for every tenant, so ... back to the drawing board.

BBing Crosby How can I send a message reply from an application command using my Discord Bot ...

Bing Crosby•7/7/24, 8:23 PM

To follow up on this, is it even possible? Or can the bot only respond in the text channel where the application command was triggered from?

BBing Crosby To follow up on this, is it even possible? Or can the bot only respond in the te...

Hello, I’m Allie!•7/7/24, 8:33 PM

If your bot has message send permissions, then yes

user•7/8/24, 4:18 PM

just double checking, ctx.waitUntil executes the promise after the worker returns, right?

user•7/8/24, 4:29 PM

hmm

user•7/8/24, 4:29 PM

is there a way to make it so the code executes after it returns?

user•7/8/24, 4:30 PM

like a promise for request finished or whatever

user•7/8/24, 4:30 PM

I'm trying to make it so my http interactions bot edits the message after initially acknowledging it

Original message was deleted

user•7/8/24, 4:30 PM

was just typing that out haha

user•7/8/24, 4:31 PM

uhhh, I'm not sure how I'd do that with how my structure is rn

user•7/8/24, 4:32 PM

I'm just doing it how I saw others do it lol

user•7/8/24, 4:32 PM

export default {
    async fetch(request: Request, env: Env, ctx:EventContext<Env,any,any>) {
        const url = new URL(request.url);

        if (url.pathname !== "/interactions") {
            return Response.redirect(
                "https://github.com/User9684/user-utils",
                301
            );
        }

        const verified = await VerifyRequest(request, env);
        if (!verified) {
            return new Response("erm, no???", {
                status: 401,
            });
        }

        const requestBody: Interaction = await request.json();

        ctx.waitUntil(await (async () => {

        })())

        return Response.json({
            type: CallbackType.DEFERRED_CHANNEL_MESSAGE_WITH_SOURCE
        })
    },
};

export default {
    async fetch(request: Request, env: Env, ctx:EventContext<Env,any,any>) {
        const url = new URL(request.url);

        if (url.pathname !== "/interactions") {
            return Response.redirect(
                "https://github.com/User9684/user-utils",
                301
            );
        }

        const verified = await VerifyRequest(request, env);
        if (!verified) {
            return new Response("erm, no???", {
                status: 401,
            });
        }

        const requestBody: Interaction = await request.json();

        ctx.waitUntil(await (async () => {

        })())

        return Response.json({
            type: CallbackType.DEFERRED_CHANNEL_MESSAGE_WITH_SOURCE
        })
    },
};

user•7/8/24, 4:32 PM

ignore the insanely wrong usage of waitUntil

Original message was deleted

user•7/8/24, 4:32 PM

oh sorry I read this wrong

user•7/8/24, 4:32 PM

dyslexia

user•7/8/24, 4:33 PM

read it as waituntil after returning haha

user•7/8/24, 4:33 PM

well I don't even need to do that haha

user•7/8/24, 4:34 PM

i should just need to do waitUntil(handleInteraction) i believe

user•7/8/24, 4:34 PM

considering the edit happens there :p

user•7/8/24, 4:35 PM

yeah lol its too long for a small snippet of code

user•7/8/24, 4:35 PM

didnt wanna flood too bad

Original message was deleted

user•7/8/24, 4:37 PM

also isnt this incorrect syntax?

user•7/8/24, 4:37 PM

still a bit unsure on waitUntil syntax but the typechecker yells at me for that :p

Original message was deleted

user•7/8/24, 5:17 PM

yeah

user•7/8/24, 5:17 PM

user•7/8/24, 5:18 PM

but thats not my issue rn so its whatever lol

EEisenbergEffect When I create a new application via the Cloudflare dashboard, I see the option t...

Chaika•7/9/24, 2:21 AM

Can use something like : https://github.com/cloudflare/wrangler-action
Longer term convergence of Pages and Workers is planned: https://blog.cloudflare.com/pages-workers-integrations-monorepos-nextjs-wrangler#:~:text=Workers%20CI/CD.%20Later%20this%20year%2C%20we%20plan%20to%20bring%20the%20CI/CD%20system%20from%20Cloudflare%20Pages%20to%20Cloudflare%20Workers.%20Connect%20your%20repositories%20to%20Cloudflare%20and%20trigger%20builds%20for%20your%20Workers%20with%20every%20commit.

GitHub

GitHub - cloudflare/wrangler-action: 🧙‍♀️ easily deploy cloudflare ...

easily deploy cloudflare workers applications using wrangler and github actions - cloudflare/wrangler-action

The Cloudflare Blog

Announcing Pages support for monorepos, wrangler.toml, database int...

Today, we’re launching four improvements to Pages that bring functionality previously restricted to Workers, with the goal of unifying the development experience between the two. Support for monorepos, wrangler.toml, new additions to Next.js support and database integrations!

Coshmar Tabletowy V•7/9/24, 12:01 PM

Hi all, anyone is experiencing issue with .workers.dev and .pages.dev subdomains?

Coshmar Tabletowy V•7/9/24, 12:01 PM

it seems I am unable to resolve my domains today at all

Erisa•7/9/24, 12:25 PM

Probably your isp or country misunderstanding how public suffixes work and blocking them

fletcher3•7/9/24, 2:34 PM

Hi there. I would really love to use the new Rate Limiting service for my Cloudflare Pages next.js app in some route handlers. Could you already give an estimation on if and when the beta will be accessible as a binding for cloudflare pages and when it will move out of beta. Thank you and keep building :))

freerangebella•7/10/24, 4:18 AM

Hi I have some questions about workers - if I have a backend python process that typically takes 3-4 minutes could that scale well with workers, or would it quickly get to be too expensive? I'm not sure I understand how this would work with the pricing model. It's an image processing thing and I'm not sure I can do much more to optimize it

cole•7/10/24, 12:25 PM

Does anyone know off-hand if the

net

net

and

socks

socks

node packages are supported by Workers? I don't see them here, which makes me think not

https://developers.cloudflare.com/workers/runtime-apis/nodejs/

Cloudflare Docs

Node.js compatibility · Cloudflare Workers docs

Implemented Node.js runtime APIs and enablement instructions for your Worker project.

rob•7/10/24, 4:22 PM

when you serveStatic on a worker, and it does its pulling from the KV it makes for you-- Do you get charged per read on that per static page load?

Rrob when you serveStatic on a worker, and it does its pulling from the KV it makes f...

Hard@Work•7/10/24, 4:25 PM

Per read from KV(which is why we recommend Pages instead, where reads are free)

rob•7/10/24, 4:26 PM

yeah.. makes sense. Im trying to figure out a way to deploy static frontends for my WfP scripts and i thought maybe thatd be an easy way to do it all in one go.. instead of trying to reverse engineer or pages gets files pushed to it , no documented RESt API for that anywhere.

Rrob yeah.. makes sense. Im trying to figure out a way to deploy static frontends for...

Hard@Work•7/10/24, 4:27 PM

Yeah, iirc Pages is only meant to be uploaded to via

wrangler

wrangler

/the Dashboard

rob•7/10/24, 4:33 PM

Anyone on WfP have any suggestions on how we could go about that outside of just running our own kind of pages deploymebt , i can dig thru wrangler code and see whats going on

rob•7/10/24, 4:33 PM

the KV serving would be easiest but then the cost issue as you said.

rob•7/10/24, 4:37 PM

I guess I could use a github action script and do itl ike that too

Luke•7/10/24, 5:14 PM

Is there a work around for Worker Routes to run on home page requests with query params but not run on everything else?
Example: If I add a route for

*/*

*/*

it will run for all traffic (this is too broad), if I add one for

*/

*/

it will only run for the home page if there aren't any query params.

whois | API man•7/10/24, 5:15 PM

Can I do something with workers to allow custom domains for my app?
Like, something to make CNAMEs so that others can add it to their domain and that way their domain becomes an alias of mine?

Wwhois | API man Can I do something with workers to allow custom domains for my app? Like, someth...

Chaika•7/10/24, 5:33 PM

https://developers.cloudflare.com/cloudflare-for-platforms/cloudflare-for-saas/start/advanced-settings/worker-as-origin/

Chaika•7/10/24, 5:33 PM

CF For SaaS is your friend, you get 100 custom hostnames for free

LLuke Is there a work around for Worker Routes to run on home page requests *with quer...

Chaika•7/10/24, 5:34 PM

Route pattern matching considers the entire request URL, including the query parameter string. Since route patterns may not contain query parameters, the only way to have a route pattern match URLs with query parameters is to terminate it with a wildcard, *.

https://developers.cloudflare.com/workers/configuration/routing/routes/#route-patterns-may-not-contain-any-query-parameters

CChaika > Route pattern matching considers the entire request URL, including the query p...

Luke•7/10/24, 5:35 PM

The problem with this is that if I only want to run the worker on the home page and I terminate the route with a wildcard it matches 100% of all URLS, not just the home page route

. E.G- it will match too

LLuke The problem with this is that if I only want to run the worker on the home page ...

Chaika•7/10/24, 5:36 PM

yea, I get what you want, some people have asked for that before, it's just as the docs say though

export default { async fetch(request: Request, env: Env, ctx:EventContext<Env,any,any>) { const url = new URL(request.url); if (url.pathname !== "/interactions") { return Response.redirect( "https://github.com/User9684/user-utils", 301 ); } const verified = await VerifyRequest(request, env); if (!verified) { return new Response("erm, no???", { status: 401, }); } const requestBody: Interaction = await request.json(); ctx.waitUntil(await (async () => { })()) return Response.json({ type: CallbackType.DEFERRED_CHANNEL_MESSAGE_WITH_SOURCE }) }, };