Quoted post unavailable.
No post body was provided.
Cloudflare Pages: Best server tech since CGI-bin?
151–160 of 226 posts
Re: Cloudflare Pages: Best server tech since CGI-bin?
#152CF workers currently can’t do anything that requires a socket right?
Re: Cloudflare Pages: Best server tech since CGI-bin?
#153CF workers currently can’t do anything that requires a socket right?
They can with Durable Objects, but you'll pay $12.50/million GB-s while each connection is open (which is about $93.75/million minutes).
It's currently not very competitive with the likes of AWS API Gateway at $0.25/million minutes.
Re: Cloudflare Pages: Best server tech since CGI-bin?
#154What is really annoying is that Cloudflare pages will strip the file extension off of your html pages, and perform permanent redirects to those new URLs. Now if you're intending on moving to a new hosting service that doesn't do that (cgi-bin), all Google search results to your site will 404. Github pages and likely others also supports this format, so moving between those two services doesn't exhibit this problem. M…
You can use the more barebones Worker Sites and retain file extensions. Pages has nicer UX (automatic PR preview sites!) but the old school Worker Sites setup is dead simple and does exactly what you want - it's just a template setup to load assets from KV storage.
Re: Cloudflare Pages: Best server tech since CGI-bin?
#155The rest of the industry haven't even started figuring out what Cloudflare Pages Functions + Durable Objects can do. Workers can also send emails for free, and soon you will be able to process them as well with Email Workers. Cloudflare also doesn't charge you for egress either.
Weary of free as in beer. Often it is better to pay, for a situation where you are the actual customer.
They made emails and egress free because there is a lot of price gouging going on in the industry that stops people from starting businesses.
https://blog.cloudflare.com/aws-egregious-egress/
Identity as service is another category that's egregiously priced, and it's usually priced based on monthly active users too, which is the worst. It would be great to see Cloudflare disrupting that one as well.
Re: Cloudflare Pages: Best server tech since CGI-bin?
#156Earlier quoted context omitted.
Having .html file extensions is very old school, and its removal is one of the popular/default redirects on all http servers that support it. Site generators also hide it through various methods (e.g. having a folder with the path name with just an index.html where a dynamic redirect isn't possible).
Yes. New school's defining feature is needless layering of complexity to hide the simple truth of the file system from users.
My web server is not exposing file system paths to the user, it is deciding on content programmatically and it’s purely an aesthetic coincidence that the url path looks like a file system path.
Re: Cloudflare Pages: Best server tech since CGI-bin?
#157In 10 years time when cloudflare goes bankrupt/withdraws the free offering, will you be able to redeploy to another platform or will you start having to delve into 10 year old code and porting it to a new API? Is there at least an nginx-cloudflare module that lets you self-host this stuff?
You mostly use standard Web APIs inside Workers, so that's portable, but the entire runtime (including Durable Objects, KV, R2 and D2) is open-source and can be self-hosted.
https://blog.cloudflare.com/workerd-open-source-workers-runt...
Re: Cloudflare Pages: Best server tech since CGI-bin?
#158Earlier quoted context omitted.
Weary of free as in beer. Often it is better to pay, for a situation where you are the actual customer.
They made emails and egress free because there is a lot of price gouging going on in the industry that stops people from starting businesses. https://blog.cloudflare.com/aws-egregious-egress/ Identity as service is another category that's egregiously priced, and it's usually priced based on monthly active users too, which is the worst. It would be great to see Cloudflare disrupting that one as well.
This. At this point in everything being "cloud native" fewer and fewer people and orgs have any experience building internet networks - buying transit (circuits), peering, etc.
For players at Cloudflare, AWS, GCP, etc scale it's essentially free. The fact that many of them (other than Cloudflare) charge $0.08/GB or whatever for egress and that's just accepted because people think "that's what it costs" is wild to me.
My personal conspiracy theory of sorts is that many compute, storage, etc products from big cloud providers are essentially priced as loss leaders because while the average dev has some idea of what a GB of storage, GHz CPU, etc costs (because they priced a laptop) they have no idea how bandwidth and connectivity is priced at this level and cloud providers capitalize on that (somewhat understandable) ignorance.
Re: Cloudflare Pages: Best server tech since CGI-bin?
#159Meh I prefer Cloudfront
Re: Cloudflare Pages: Best server tech since CGI-bin?
#160I am waiting for the time where we can host WordPress freely with static hosting and workers for admin ui/dynamic content. Otherwise static websites are only for devs.
They have a product for that https://www.cloudflare.com/pg-lp/speed-up-wordpress-with-clo... It caches all pages on Cloudflare and only bypasses Cache on Cookies such as `wp-. |wordpress. |comment_. |wordpress_logged_. ` which is used by /wp-admin/ are and when someone posts a comment. This turns your WP into static without doing anything special. Or you can write a custom cache rule for cookies using "Page Rules" or…
I used wp2static to archive a WordPress site recently, and I am disappointed with the performance.
The same website without Cloudflare CDN and just using a simple caching plugin is much faster than the exported version by wp2static hosted on Cloudflare pages.
It has fallen from 99 to 78 in the mobile page speed test.
I tried creating a copy of the website using wget, it was faster but i faced issues with missing files and posts on the main page using temporary query links and not the permanent links.
So I went through the Hassle of compiling wp2static and just eating the performance loss instead.