Using external dns or CF Dns? Previews on custom domains only work with CF DNS
Using external dns or CF Dns? Previews on custom domains only work with CF DNS
Ewell I delegated a subdomain to cloudflare dns
Enot the entire domain
CPartial cname/Business setup or Partial ns/Ent setup?
Ehm I am not sure about this; Is there a way to check which setup I have in place?
I registered two new NS records for my subdomain on my external dns setup then registered the parent domain in cloudflare dns and set some CNAME up
I registered two new NS records for my subdomain on my external dns setup then registered the parent domain in cloudflare dns and set some CNAME up
Cyou setup ns records for a subdomain in your external dns, and then added the parent domain in CF? That doesn't make sense for either
If you have Business plan, then cname partial setup is the only thing you could have done
You'd need Enterprise to do partial domain setup w/ delegated nameservers.
If you have neither, then you did something else lol. If you can share the subdomain of your attempt to do above, could see
If you have Business plan, then cname partial setup is the only thing you could have done
You'd need Enterprise to do partial domain setup w/ delegated nameservers.
If you have neither, then you did something else lol. If you can share the subdomain of your attempt to do above, could see
SHi, I want to kindly ask you what has changed with wrangler
Attaching my github actions and error images
4.0.03.114.1Attaching my github actions and error images
JThe deprecated
secret:bulkA fix was released in https://github.com/cloudflare/wrangler-action/releases/tag/v3.14.1
JDynamic importr syntax also changed a bit due to the
esbuildI'm not familiar with how
next-on-pagesOk thank you!
1Just wanted to see if anyone can provide an update on this. The Images binding is limited to 10 draws in a single operation, whereas I can fit dozens into a single call when using the original URL-based method
Bwhen creating a new cf project using cli
npm create cloudflare@latestin other words how does one control what (workers or pages) the project ends up as when creating a cloudflare project?
Bso I created a project using above command and selecting a framework and got the logs as in the attached image that says
compiled worker successfully
Bhowever when I run
wrangler dev✘ [ERROR] It looks like you've run a Workers-specific command in a Pages project.is pages and workers are names for the category that describes architecture of how the project was built?
BI know immediate response most likely be like
everything is in the docsworkers because that is what better-auth seems to support and not available in the pages
Wwhich framework? some frameworks need you to pass in an experimental flag (npm create cloudflare@latest -- --experimental), while some you can just choose workers or pages after you select the framework. it probably *is *easiest to look in the docs for the framework you're trying to use, they have the relevant command at the top 
Bastro
Wyeah that needs the flag - npm create cloudflare@latest my-astro-app -- --framework=astro --experimental
Pis it possible to setup a wildcard based route for an email worker? The e-mail address i need to process is like "test+123123@something.com" where 123123 can change
Pyep, looks like it, even the + character is not supported
AYou can setup a catch-all though, so it would catch all email sent to your domain - no idea if the catch-all catches wildcards with +’s, but perhaps an option
Pso i'm using az e-mail provider already(zoho mail) and if i setup a catch-all in cloudflare, that won't affect my other already working e-mail addresses?
Pyes, the point is that i'm trying to process the e-mail with code and the e-mail address woudl contain the user id
Pso trying to find an easy way to do that, email workers seemed like a good option
HWould it work if you put it on a subdomain?
Pi think you can't setup catch-all for subdomains, on cloudflare at least
P"Catch-all rule only applies on the zone-level domain, you can’t create catch-all rule for each of your subdomain."
HWhat if you set a forward in Zoho, toward a subdomain? So forward to auto@sub.doma.in?
Pdamn, turns out theres webhook support in zoho mail itself
HWell, that works too!
P
HMaybe startsWith instead of contains?
Pyeah i'll got it from there, thanks. Anyway, feature request: support wildcards for email workers routing 
CYou can use a wildcard catch-all, and then parse the email address out
CCatch-all would apply to subdomains but you can't configure per subdomain, if that makes sense. You could just add a subdomain and not your root domain to email routing, or just handle it all through a worker
Pbut if i enable catch-all, i need to update the mx records to cloudflare's server, no? In that case i would lose access to Zoho Mail.
CIf you wanted emails for your apex/root (email@domain.com) to go to Cloudflare, yea you'd have to pick one or the other. Could just use a subdomain though (email@sub.domain.com)
Cthat's a limitation in just how email works
Psubdomain would be fine, but it says "Subdomains are dependent on domain. If domain is disabled, subdomains will be disabled too." on the email routing settings screen(where it displays what MX records i need to setup)
Por i should just ignore that and set up the cloudflare mx records for a subdomain?
Cannoyingly that's still wrong in the ui. It's indeed not true, just tested again now, you can receive mail on subdomains without enabling the domain itself
Cyou can just add a subdomain under Email routing settings, it'll do the records for you
HHello, does anyone knows if I can install a non js dependency in Workers Build ? I tried adding a build variable
Edit : Figured it out, using
UNSTABLE_PRE_BUILD
curl -fsSL https://d2lang.com/install.sh | sh -s --Edit : Figured it out, using
SKIP_DEPENDENCY_INSTALLSo basically i setup a subdomain with cloudflare MX, setup catch-all and since the MX is only on the subdomain, it will only catch-all the subdomain email address, which then i can forward to a worker. In theory this could work.
Cdoes pages not support
env