uhh to be able to use the full CloudFlare Service you need to change the Nameservers because CloudFlare acts in many cases like a Middleware. Client <-> CloudFlare <-> Your Server idk if its really possible and is really worth anything
Are you only wanting to restrict viewing the demo by IP or something a bit less serious than a full tunnel? You could use the WAF for that instead of Cloudflared/tunnels
funny story though: my email was cloudflare@mydomain at first, and Cf's Zendesk named me "cloudflare" because of it lol, showed that way in tickets too. I always use myrealname@company.mydomain now
Cashapp doesn’t let you sign up with emails like cashapp@yourdomain, couldn’t figure out the issue without contacting their support. The error message was generic
D1 is SQLite but there's no SQLite protocol or anything like that, so you'd have to have it use the http api or build an http api in a worker for it. MediaWiki has some abstraction for database access it looks like: https://doc.wikimedia.org/mediawiki-core/master/php/classWikimedia_1_1Rdbms_1_1Database.html, you'd have to implement a new database type and all those funcs, not possible to do built in. There is an SQlite option there but that'd be just for local sqlite
So, small to medium Minecraft server networks usually consume more than 1 Tb of traffic per month, and Cloudflare Spectrum's pricing is $1/GB for ingress traffic as it is a proxy. And if we think we receive 1 Tb traffic per month, our bill would come up to about $1,019/month. So I'd like to ask that is Spectrum made for really large Minecraft server networks?
yea sadly Spectrum for Pay as you go plans is more of a teaser/trial. You'd need to go Enterprise to get custom pricing, and that's a few thousand/month min
For example, an usage case for it would be implementing a L7 protection using the capacity of Magic Transit since I think Magic Transit doesn't have L7 support for many apps
You can (1) Put your domain on Cloudflare, you probably already did (2) Set a CNAME record to your Digital Ocean app, or whatever instructions for domains they provide (3) Use a Cloudflare WAF rule to show a block page to anyone who visits that subdomain that doesn't match rules you set, like IP address or having some kind of secret token in the link.
I may not have made that message crystal clear enough: My suggestion was NOT meant to indicate that you should just blindly raise the TTL, if that was how it was understood.
Some use-cases (e.g. slowly / almost never changing data) can typically be cached for a (very) long time, in which case it would typically make absolutely no sense, to keep it alone on 600 seconds / 10 minutes. How far you could eventually go, would be depending on various different criteria though.
Looking at your elaboration later on, it does actually sound like it would justify for a long(er) TTL than the 600 seconds / 10 minutes. Maybe even longer than the 3600 seconds / 1 hour, that you indicated you raised it to.