Interesting, just competition for netlify, vercel etc I guess.
Weird use of capitalized JAM... it's been accepted for a good portion of the year to now be Jamstack I thought.
Cloudflare Pages: the best way to build JAMstack websites
31–40 of 89 posts
Re: Cloudflare Pages: the best way to build JAMstack websites
#32I’d love to see a version of this (or Netlify, Vercel, etc) that didn’t bundle CI with the preview and deploy steps so that I can pick my own CI and then effectively use the “CDN” as the highly qualified host of my static assets.
Me too. I hate that Vercel and Netlify limit my build to using Node v12 because that is what Amazon supports. Node v14 is LTS now but still no telling when it will be a supported runtime. I refuse to live without optional chaining!
Re: Cloudflare Pages: the best way to build JAMstack websites
#33This is probably going to go somewhere, and it's good to see Netlify get some more competition, but this announcement kind of lost me at: > There are no great solutions. Therea are plenty of existing solutions here that do pretty much the same thing, including Netlify, Vercel, and going all the way back to Heroku. Cloudflare is expanding their product line, which is fine, but lets not pretend that this is some brand…
There is some marketing here to be sure, but in some sense, they are at least partially right in that: - they aren’t just reselling AWS services (if I recall correctly Netlify and to at least some extent Vercel do, for instance) - They will be providing their own database platform (coming soon according to the blog post, as of 12/17/2020) which means they can provide the ability to have a single end to end provider f…
Yes, Cloudflare's offering here has promises of adding more functionality in the future, but I don't think that changes my point. At the moment, it is fundamentally the same as existing tools.
"Worker" functionality is already available on both Netlify and Vercel.
Cloudflare's version will obviously have a tighter integration into the rest of Cloudflare.
I've written up a summary of tools/options in this space in the past (but it is a bit out-of-date, but space is moving fast). Including Cloudflare Pages, I now count 6 platform-add-on features that cover all of this functionality.
https://www.nrmitchi.com/2020/10/state-of-continuous-product...
Re: Cloudflare Pages: the best way to build JAMstack websites
#34I'm currently using Netlify for my personal website and it works flawlessly. The only thing that would make me go to Cloudflare is the 500 builds per month, no mentions of build time. While Netlify is limited to 300 minutes of build time per month, in free tier.
Re: Cloudflare Pages: the best way to build JAMstack websites
#35Other exciting news from article: > Over the coming months, we’ll be working on integrating Workers and Pages into a seamless experience. It’ll work the exact same way Pages does: just write your code, git push, and we’ll deploy it for you. The only difference is, it won’t just be your frontend, it’ll be your backend, too. And just to be clear: this is not just for stateless functions. With Workers KV and Durable Obj…
I think it would be extremely useful to have some type of simple authentication system for the preview URLs. I think the One-Time Pin Login [1] available with Cloudflare Access would be a really great fit if I could drive it from a list of email addresses in the GitHub repo.
As a use case, consider a small project where someone is looking for very preliminary feedback and wants to ask friends, family, trusted colleagues, etc. for feedback on non-public previews, but without the burden of a full blown authentication system.
I suppose that depends on whether or not it supports private repos. I don't like the systems that require public repos.
1. https://developers.cloudflare.com/access/authentication/conf...
Re: Cloudflare Pages: the best way to build JAMstack websites
#36What if I already have static HTML and just need a host? No builds (I do them locally), no frameworks, just an HTML structure. I'd love to just be able to point to a git repo and have the site published through Cloudflare, since it already sits in front of my site anyway.
Re: Cloudflare Pages: the best way to build JAMstack websites
#37CloudFlare has leveraged the fact that they are pretty close to the sole provider of DDoS (which 99% of people don't need to worry about) beautifully.
Once your in for the DNS/DDoS/Nginx-as-a-service adding anything else is a matter of hop/latency minimization. Like I love and use Netlify but I'm always happy to reduce hops where I can.
Re: Cloudflare Pages: the best way to build JAMstack websites
#38What if I already have static HTML and just need a host? No builds (I do them locally), no frameworks, just an HTML structure. I'd love to just be able to point to a git repo and have the site published through Cloudflare, since it already sits in front of my site anyway.
Hi there, I'm the PM working on Cloudflare Pages. We don't have support for this now since we're still in beta, so not everything is there yet, but it's certainly a use case we intend to support. You'll just be able to specify no build step. :)
Re: Cloudflare Pages: the best way to build JAMstack websites
#39What if I already have static HTML and just need a host? No builds (I do them locally), no frameworks, just an HTML structure. I'd love to just be able to point to a git repo and have the site published through Cloudflare, since it already sits in front of my site anyway.
Linked in response to a question I asked below, it seems like you can use CloudFlare Workers to host a static site: https://developers.cloudflare.com/workers/platform/sites
But also, from reading the Pages docs I wager you can also make the build command something like `echo done` and then set the build directory in your configuration to be `.`.
Re: Cloudflare Pages: the best way to build JAMstack websites
#40Earlier quoted context omitted.
There is some marketing here to be sure, but in some sense, they are at least partially right in that: - they aren’t just reselling AWS services (if I recall correctly Netlify and to at least some extent Vercel do, for instance) - They will be providing their own database platform (coming soon according to the blog post, as of 12/17/2020) which means they can provide the ability to have a single end to end provider f…
Yes, Cloudflare's offering here has promises of adding more functionality in the future, but I don't think that changes my point. At the moment, it is fundamentally the same as existing tools. "Worker" functionality is already available on both Netlify and Vercel. Cloudflare's version will obviously have a tighter integration into the rest of Cloudflare. I've written up a summary of tools/options in this space in the…
It is fundamentally different: concerning service offerings, your static site and your edge cache can both be handled by CloudFlare.
Maybe that’s a nitpick, but it probably feels earth-shattering to some, because it recategorizes CloudFlare as a first-class hosting provider (and soon-to-be application and database layer), not just a cache. Sort of like how Redis is now a first-class database, at least according to them.
Personally, I’m excited about this because it finally represents an edge someone has (no pun intended) that could compete with AWS’s services for JAMStack-style sites and apps.