To follow up on this, is it even possible? Or can the bot only respond in the text channel where the
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?
HIf your bot has message send permissions, then yes
Ujust double checking, ctx.waitUntil executes the promise after the worker returns, right?
Uhmm
Uis there a way to make it so the code executes after it returns?
Ulike a promise for request finished or whatever
UI'm trying to make it so my http interactions bot edits the message after initially acknowledging it
Uwas just typing that out haha
Uuhhh, I'm not sure how I'd do that with how my structure is rn
UI'm just doing it how I saw others do it lol
UUignore the insanely wrong usage of waitUntil
Uoh sorry I read this wrong
Udyslexia 
Uread it as waituntil after returning haha
Uwell I don't even need to do that haha
Ui should just need to do waitUntil(handleInteraction) i believe
Uconsidering the edit happens there :p
Uyeah lol its too long for a small snippet of code
Udidnt wanna flood too bad
Ualso isnt this incorrect syntax?
Ustill a bit unsure on waitUntil syntax but the typechecker yells at me for that :p
Uyeah
U:p
Ubut thats not my issue rn so its whatever lol
CCan 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.
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
easily deploy cloudflare workers applications using wrangler and github actions - cloudflare/wrangler-action
easily deploy cloudflare workers applications using wrangler and github actions - cloudflare/wrangler-actionThe Cloudflare Blog
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!
CHi all, anyone is experiencing issue with .workers.dev and .pages.dev subdomains?
Cit seems I am unable to resolve my domains today at all
EProbably your isp or country misunderstanding how public suffixes work and blocking them
FHi 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 :))
FHi 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
CDoes anyone know off-hand if the and 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/
https://developers.cloudflare.com/workers/runtime-apis/nodejs/
Cloudflare Docs
Implemented Node.js runtime APIs and enablement instructions for your Worker project.
Rwhen 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?
HPer read from KV(which is why we recommend Pages instead, where reads are free)
Ryeah.. 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.
HYeah, iirc Pages is only meant to be uploaded to via /the Dashboard
RAnyone 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
Rthe KV serving would be easiest but then the cost issue as you said.
RI guess I could use a github action script and do itl ike that too
LIs 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.
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.
WCan 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?
Like, something to make CNAMEs so that others can add it to their domain and that way their domain becomes an alias of mine?
CCF For SaaS is your friend, you get 100 custom hostnames for free
CRoute 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
LThe 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
/yea, I get what you want, some people have asked for that before, it's just as the docs say though
Cif you a paid zone you could work around it with snippets (although they're alpha/not recommended for production yet), either doing the logic in a snippet directly or fetching a worker on a subdomain, and then they're powered by ruleset engine so you could have it check only if any query params are set (len > 0), or for a specific one, etc
Woh, 100? and how much would cost more?
Wi think to begin with 100 is nice
C$0.10/per hostname/per month