[deleted]
Cloudflare Pages: Best server tech since CGI-bin?
91–100 of 226 posts
Re: Cloudflare Pages: Best server tech since CGI-bin?
#92Earlier quoted context omitted.
Yes, let's simplify the Internet, being decentralised is such a crutch! We should all just connect directly to Cloudflare.
You go ahead and play "being decentralised" with your buddies while people in the real world just mind their own business doing whatever they need to do using the current right tool for the job(in this case Cloudflare being the tool).
People in the real world, who just cheerfully do business, with zero thought of impact or consequences of their actions beyond next paycheck, have put us in this awesome economic situation, we all know and enjoy.
Surely blindly pushing, yet another corporation into position, where they can lobby virtually anything, is awesome idea. (Nothing against folks from cloudflare. They seem all right, but they will get acquired and/or change leadership at some point).
Re: Cloudflare Pages: Best server tech since CGI-bin?
#93Earlier quoted context omitted.
Maybe this is just me, but I like that I can decouple the way I organize my file system from the way users access my site. And with that comes the ability to get rid of file extensions and make urls more human-friendly. Remember, not every person has file extensions turned on by default on their Windows File Explorer!
Quoted post unavailable.
Ok, I set myself up for that.
Do you have experience running websites that cater to the non tech savvy? How are your urls set up? Do they get confused where to find things? Do you use a database? Do you dynamically render content using templates?
Re: Cloudflare Pages: Best server tech since CGI-bin?
#94Earlier quoted context omitted.
Yes, let's simplify the Internet, being decentralised is such a crutch! We should all just connect directly to Cloudflare.
You go ahead and play "being decentralised" with your buddies while people in the real world just mind their own business doing whatever they need to do using the current right tool for the job(in this case Cloudflare being the tool).
In nature, a lack of genetic diversity in a species isn't typically much of a problem until there's an extinction event, and then it can be a big problem.
You might not feel the downsides of having a huge percentage of the internet going through a single provider until it's too late to change it.
I actually quite like Cloudflare, and I don't think they're purposely doing anything nefarious (just following incentives like everyone), but I think caution is warranted.
Re: Cloudflare Pages: Best server tech since CGI-bin?
#95Earlier quoted context omitted.
Is there a reason why someone visiting your website should know or care about file extensions?
I guess no one should know whether a pdf is a pdf. Or even whether it's a .com or a .org domain - the browser should just strip all that confusing stuff away!
When you're serving someone an HTML file are you serving them the exact copy on your file system or do you ever use templates? Do you ever pull info from the database? If so, can you see why this is slightly different from directly serving a static pdf?
Also note that you'll often see a PDF generated on the fly with a long, difficult to parse URL.
Take up your second point with the W3 or whatever, to be honest if tlds weren't so important for phishing and whatnot it would probably be fine. I think some browsers have started doing that anyway. You overestimate how tech savvy the average user is, and by extension you overestimate how much the average user can keep track of all this complexity. Do you think most people have heard of .info or .xyz?
Re: Cloudflare Pages: Best server tech since CGI-bin?
#96Side note: As someone who wanted a high level overview of Durable Objects, the Cloudflare announcement page 404s https://blog.cloudflare.com/introducing-workers-durable-obje...
This sounds magical:
> Durable Objects make this easy. Not only do they make it easy to assign a coordination point, but Cloudflare will automatically create the coordinator close to the users using it and migrate it as needed, minimizing latency.
Re: Cloudflare Pages: Best server tech since CGI-bin?
#97wishlist: static page hosting for internal pages (e.g behind IP allowlists, SSO, etc...)
Re: Cloudflare Pages: Best server tech since CGI-bin?
#98Earlier quoted context omitted.
The engine is open source: https://github.com/cloudflare/workerd We did not create our own engine to create "lock-in". On the contrary, it would be a huge win for us if we could simply run FastCGI or Node or whatever applications unmodified. We'd be able to onboard a lot more customers more quickly that way! Our product is our physical network (with hundreds of locations around the world), not our specific developmen…
Are there guides for application architecture with Workers? I'm interested in Durable Objects but I don't know how to work within the 50-subrequest limit on the Free or Bundled plans. It sounds like I can only read from 50 Durable Objects or KV queries in a single request. If my usage pattern is e.g., sharing docs with many users, how would I let more than 50 users access a doc? Whether I consider fanning out on writ…
Hmm, I think there are several different reasons why the subrequest limit actually doesn't apply to your scenario.
First, Durable Objects and Workers KV requests do not count against the 50-subrequest limit. It's HTTP requests to external servers that count.
Second, with the Unbound billing model, the limit is now 1000. The old "Bundled" billing model is really intended for "configure your CDN" use cases where you're mostly just rewriting a request or response and proxying to origin. For whole applications you should use Unbound. (Note that with Durable Objects, the objects themselves always use the Unbound pricing model.)
Third, to address your specific scenario:
> If my usage pattern is e.g., sharing docs with many users, how would I let more than 50 users access a doc?
If you mean you have 50+ users connected via WebSockets and you need to send a message to each one -- these messages (on already-open WebSockets) do not count against the subrequest limit. Only starting a whole new HTTP request or new WebSocket would count.
And for "fan in", these would be incoming requests from client, but the subrequest limit applies to outgoing request. There's no limit on number of incoming requests.
Re: Cloudflare Pages: Best server tech since CGI-bin?
#99Earlier quoted context omitted.
Static hosting combined with server-side dynamic content modification using postgres was the interesting part for me. Static hosting has historically been seen as exactly that, static and immutable. Things like Cloudflare functions/workers can turn static hosting into dynamic content delivery while maintaining (most of) the benefits of static hosting. Granted, this can be done whether the underlying content is hosted…
Can you explain how Cloudflare Workers factor into hosting static pages on Cloudflare Pages vs hosting a React SPA on pages that talks to any other API? Like are the workers just serving as your backend at that point? Or are they doing something more or different as well?
the workers are regenerating the static site on postgres push
Re: Cloudflare Pages: Best server tech since CGI-bin?
#100Earlier quoted context omitted.
Quoted post unavailable.
Ok, I set myself up for that. Do you have experience running websites that cater to the non tech savvy? How are your urls set up? Do they get confused where to find things? Do you use a database? Do you dynamically render content using templates?
Not the GP here, but having run websites for the non tech savvy I can say they have no problems with any sort of URL structure because they are oblivious to URLs. They enter your-site.com into Google, click the first result (even if that’s an ad for your competitor), and then click round the links presented.