is it generally best practice to use new databases for different projects or just make new tables fo
is it generally best practice to use new databases for different projects or just make new tables for those projects?
CGenerally different databases unless they're really small or closely tied together or some special exception case
Cespecially so if you're talking about D1 I'd def recommend it, each D1 is a single threaded durable object so a new db is a nice new fresh thread not fighting with other projects
Sepic yeah
Sbecause i was writing an api and didnt know what would be better to manage all of the stuff
Si kinda just threw everything into one database
Cwhat files did you upload? Did it include an index.html at the highest level?
Shello everyone
Si have a question regarding dns
SI have the following problem:
S
Sif any can help
Sbecause i host azuracast through my unraid server and i try to connect through sambroadcaster and it fails
PYou cannot proxy (orange cloud) local ips
Pif you intend to make your website public, then that won't work
Son the server I have a tunnel with which I reach the pages of the server, but everything works from the inside to the outside, but when I try to connect from the outside and inside with the radio, it does not work
IIf you have a Cloudflare Tunnel then you should not add any DNS record manually. You need to add it as a Public Hostname within the Cloudflare Tunnels dashboard.
SI did that, but apparently something blocked the connection via sambroadcaster to the azura page
ITunnels is only for HTTP traffic if you don't have
cloudflared
MAnyone know the deeplinks docs for linking to preselected token permissions? IIRC Baselime does this during their onboarding. Would make it easier that telling people, "Okay, so go select the Workers Edit permission and name it something meaningful so you don't forget what it is" 
I'd like to add it to: https://github.com/mackenly/cloudflare-magic-linker
I'd like to add it to: https://github.com/mackenly/cloudflare-magic-linker
HGenerate an API token URL to share for usage on the Cloudflare Dashboard
MExactly!
IYou can't. If you want to redeploy you need to reupload.
IIf you want to continously deploy, that's possible yeah. Otherwise you'll need to manually redeploy (you can use the same project, you just have to reupload it all)
Poh theres actually a cooking show
Pheck
IHaha that's hilarious 
.I love the new design of the docs
DHello I am a free account user. Having trouble with an issue I know exists for others because I got 1 reply this morning.
The thread is here:
https://community.cloudflare.com/t/web-analytics-can-select-domain-but-not-select-green-button-automatic-setup/698787
The thread is here:
https://community.cloudflare.com/t/web-analytics-can-select-domain-but-not-select-green-button-automatic-setup/698787
CThanks for reporting, I replicated it and escalated the issue
Dwow ok cool
Conly if you add them both as pages custom domains in the pages project
Celse you'll 522
CSomething like:
Partial Setup works only when the root isn't using CF DNS (can't be using something using CF DNS either, like Porkbun's dns for example)
Partial setup lets you use more then one subdomain and issue certs for it, cf for saas non-ent has to have the same origin for all so you'd have to use workers or do something else
Partial setup should let you directly use some features like Pages Custom Domains/R2 Custom Domains/etc that you'd only be able to use with custom hostnames with a worker proxy
Custom Hostnames limited to one origin for entire domain, some settings like min tls take priority
Some other products aren't supported https://developers.cloudflare.com/cloudflare-for-platforms/cloudflare-for-saas/saas-customers/product-compatibility/
Partial Setup works only when the root isn't using CF DNS (can't be using something using CF DNS either, like Porkbun's dns for example)
Partial setup lets you use more then one subdomain and issue certs for it, cf for saas non-ent has to have the same origin for all so you'd have to use workers or do something else
Partial setup should let you directly use some features like Pages Custom Domains/R2 Custom Domains/etc that you'd only be able to use with custom hostnames with a worker proxy
Custom Hostnames limited to one origin for entire domain, some settings like min tls take priority
Some other products aren't supported https://developers.cloudflare.com/cloudflare-for-platforms/cloudflare-for-saas/saas-customers/product-compatibility/
Cloudflare Docs
As a general rule, settings on the customer zone will override settings on the SaaS zone. In addition, Orange-to-Orange does not permit traffic directed to a custom hostname zone into another custom hostname zone.
Cfwiw if you ignore cost/plan isn't a main concern I would go with partial just because how much cleaner it is/native to the rest of the products, but you can make custom hostnames work if need be
JWhat about if you want to have full control of
subdomain.example.comexample.comIt seems like the SaaS route probably makes more sense for that use case, right?
Cno that's the use case I mean, I would do a partial over saas
CIf you're administrating the subdomain and such
Csaas is more intended for, well, saas style products. But I mean if you don't want to pay for Business and you don't need all the cool partial stuff then saas could work
Cfor pages custom domain/r2 custom domain would need a worker proxy
Cplus messy with analytics and such, and if you have more then one looking at the dash and seeing not the actual website's name is a bit confusing lol
C
W(pls don't ping all champs for non-moderation reasons -- we see all messages 
)
)