cole
CDCloudflare Developers
•Created by cole on 4/23/2025 in #pages-help
Pages Repository Limit
How do I get in touch with the right people? Does anyone know where the limit increase form is?
2 replies
CDCloudflare Developers
•Created by Brumley Gap on 4/22/2025 in #pages-help
CNAME conflicts with TXT record name
Who is your domain provider? CNAME on the root is a big no-no because it blocks all other domain records from functioning.
Cloudflare and a few others (Namecheap) have workarounds where you can "functionally" set a CNAME at the root. (But it's really just A records)
Usually the answer is to use an A record in its place if you are using a different domain registrar. Can you confirm which registrar you are using?
2 replies
CDCloudflare Developers
•Created by cole on 3/24/2025 in #workers-help
Root directory does not restrict builds for pages
I found it!
Build watch paths! What a brilliant solution!
This works out particularly well for shared dependencies and whatnot in other peer directories!
https://developers.cloudflare.com/workers/ci-cd/builds/build-watch-paths/
2 replies
CDCloudflare Developers
•Created by cole on 2/21/2025 in #workers-help
Websockets with Workers
Sorry, didn't see that message, and don't know yet. I should be able to tell you in about a month though haha. 🤣
9 replies
CDCloudflare Developers
•Created by cole on 2/21/2025 in #workers-help
Websockets with Workers
I did things a little differently than that article hunt references.
Hope it helps!
https://www.analogous.dev/blog/websockets-and-cloudflare-workers
9 replies
CDCloudflare Developers
•Created by cole on 2/21/2025 in #workers-help
Websockets with Workers
Indeed! I ended up chasing it down - there was some error handling code that was firing at the wrong time and closing the connection in my frontend 😐 Yeah, I want those hours back haha
9 replies
CDCloudflare Developers
•Created by cole on 7/10/2024 in #workers-and-pages-discussions
Node.js compatibility · Cloudflare Worke...
Dug into this further. The answer is definitely "no" and there is a great writeup on sockets here: https://blog.cloudflare.com/workers-tcp-socket-api-connect-databases
2 replies
CDCloudflare Developers
•Created by cole on 7/10/2024 in #workers-and-pages-discussions
Node.js compatibility · Cloudflare Worke...
Found this! Looks like I may be refactoring this code a bit 😄
https://blog.cloudflare.com/workers-tcp-socket-api-connect-databases
But for TCP sockets, we faced a challenge — there was no clear shared standard across runtimes. Node.js provides the net and tls APIs, but Deno implements a different API — Deno.connect. And web browsers do not provide a raw TCP socket API, though a WICG proposal does exist, and it is different from both Node.js and Deno.
2 replies
CDCloudflare Developers
•Created by freerangebella on 7/10/2024 in #workers-and-pages-discussions
Hi I have some questions about workers
I'm not super savvy on the pricing either, but 3-4 minutes of computation sounds like not the right fit for Workers in my conceptualization of them. What I have done for processes like that is build a queue that gets fired into a Go process somewhere else for the CPU/GPU workload
1 replies
CDCloudflare Developers
•Created by cole on 7/3/2024 in #workers-and-pages-discussions
I want to check on whether I am missing
I think my short term aim will be to just set up a route for every custom hostname 🤷♂️
1 replies
CDCloudflare Developers
•Created by Chaika on 7/2/2024 in #workers-and-pages-discussions
Right, CF For SaaS enables that. You can
Ahh perfect. Thanks so much for your help! And the pointer to what's happening in the industry - I'm super interested in following those developments!
24 replies
CDCloudflare Developers
•Created by Chaika on 7/2/2024 in #workers-and-pages-discussions
Right, CF For SaaS enables that. You can
Or I may have skipped the pre-validation TXT... that seems like something I might have done haha 😅
24 replies
CDCloudflare Developers
•Created by Chaika on 7/2/2024 in #workers-and-pages-discussions
Right, CF For SaaS enables that. You can
Ahh nice. Thanks! That's great to know! I also may have been too impatient - very used to how fast validation works for domains on Cloudflare haha. (and non-root CNAMEs)
24 replies
CDCloudflare Developers
•Created by Chaika on 7/2/2024 in #workers-and-pages-discussions
Right, CF For SaaS enables that. You can
That's exciting!! Thank you! 😄
24 replies
CDCloudflare Developers
•Created by Chaika on 7/2/2024 in #workers-and-pages-discussions
Right, CF For SaaS enables that. You can
Just for completeness.. these are the ideas I was throwing around to improve this situation.
- get the industry to standardize on some mechanism of "CNAME at the root" that can be interpreted from the outside. I.e. Naively: a TXT record that indicates that a "CNAME" Is in place, even if it just looks like A records
- Teach Workers to be more savvy about recognizing "appropriate A records" as validating the "CNAME" requirement on root domains
- Create a TXT or other mechanism to short circuit Cloudflare's CNAME recognition and indicate that A records are really being resolved properly as a "CNAME at the root"
24 replies
CDCloudflare Developers
•Created by Chaika on 7/2/2024 in #workers-and-pages-discussions
Right, CF For SaaS enables that. You can
Ok cool - I'll give that a shot, thank you!
24 replies
CDCloudflare Developers
•Created by Chaika on 7/2/2024 in #workers-and-pages-discussions
Right, CF For SaaS enables that. You can
Yeah, that makes sense.
It's just hard if I want someone to be able to use my service and they use another domain provider, my workers are sorta hosed haha
24 replies
CDCloudflare Developers
•Created by Chaika on 7/2/2024 in #workers-and-pages-discussions
Right, CF For SaaS enables that. You can
Yeah, exactly. It worked out ok for this case because I just flipped the domain over to being managed by Cloudflare, but I can't imagine that will always work haha
24 replies