Cloudflare Pages: Best server tech since CGI-bin?

Post by lmz » Mon, Oct 24, 2022, 10:43 AM UTC

mhensley wrote: post #154

untitaker_ wrote: post #5

What 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. https://developers.cloudflare.com/workers/platform/sites/

Post by dzikimarian » Mon, Oct 24, 2022, 11:02 AM UTC

palata wrote: post #200

dzikimarian wrote: post #198

Earlier quoted context omitted.

15 years ago Google was considered cool :-)

And 15 years ago it was cool, wasn't it?

Post by rakoo » Mon, Oct 24, 2022, 11:16 AM UTC

qbasic_forever wrote: post #134

rakoo wrote: post #131

Earlier quoted context omitted.

> Plain old CGI doesn't scale beyond toy usage--it spawns a process per request. I'd be willing to bet the opposite: CGI is more than enough for 80% of workload, performance-wise. There are a few good reasons why CGI isn't the best today: the tooling doesn't exist, the security model is really bad, and you can cram fewer websites on a single machine, so for the same number of websites you need more machines, and that…

Sure but developers don't want to bifurcate their service code and releases into a simple version using CGI and a dedicated app server version for when CGI doesn't scale for them or their users. They just want to write one python web app and run it everywhere. There's no way a CGI app can reach a million requests a second on the same hardware that a nodejs (single thread, worker loop) would take to do 1M RPS. Process…

Post by josephg » Mon, Oct 24, 2022, 12:30 PM UTC

rakoo wrote: post #204

josephg wrote: post #180

Earlier quoted context omitted.

Yep. Also, sharing resources between connections is (at best) very difficult using CGI, and its trivially easy using a stand-alone app server. You can just set up a global variable at process startup and you're done. (This is useful in just about every web app I've ever written - eg for the connection to a database, cached resources, cached renders of common pages, in-memory only security tokens, etc). I also find th…

> Also, sharing resources between connections is (at best) very difficult using CGI, and its trivially easy using a stand-alone app server. You can just set up a global variable at process startup and you're done You can pass environment variables to CGI scripts as well. In fact, that's exactly how CGI works. Shared resources can be cached in memory through redis, although a shared file (for example sqlite) is enough…

Post by rakoo » Mon, Oct 24, 2022, 1:02 PM UTC

josephg wrote: post #207

rakoo wrote: post #204

Earlier quoted context omitted.

> Also, sharing resources between connections is (at best) very difficult using CGI, and its trivially easy using a stand-alone app server. You can just set up a global variable at process startup and you're done You can pass environment variables to CGI scripts as well. In fact, that's exactly how CGI works. Shared resources can be cached in memory through redis, although a shared file (for example sqlite) is enough…

Environment variables can’t store a TCP connection to a database or a pre rendered HTML string. In the latter case you could use redis, but that’s a poor, inconvenient, inefficient replacement for a global variable.