Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Cloudflare Pages: the best way to build JAMstack websites

blog.cloudflare.com

Post reply on HN
Print view View original

61–70 of 89 posts

Re: Cloudflare Pages: the best way to build JAMstack websites

#61

Post by Earwig »

Animats wrote: post #55

Check their terms.[1] First of all, you're giving them a license to your content for their purposes. "By submitting, posting, or publishing your content, suggestions, enhancement requests, recommendations, feedback, information, data, or comments (“Content”) to any Website or Online Service, you are granting Cloudflare a perpetual, irrevocable, worldwide, non-exclusive, royalty-free right and license (with the right…

Crucial definitions:

> “Websites” refers to www.cloudflare.com, as well as the other websites that Cloudflare operates and that link to these Terms, and (ii) “Online Services” means Cloudflare’s products and services that are publicly available without a subscription or a Cloudflare account, including, but not limited to, the 1.1.1.1 Public DNS Resolver service, including 1.1.1.1 for Families, Cloudflare Time Services, and RPKI Portal.

Re: Cloudflare Pages: the best way to build JAMstack websites

#63

Post by toddmorey »

no_wizard wrote: post #20

I was wondering when this was going to happen! This is a legitimate contender here against Gatsby, Netlify, AWS Amplify and the like One thing I like about this over all the others is they aren’t (to my knowledge) just reselling AWS features with added convenience (not that this is an issue or bad, but this a lot of what Netlify does with their lamdas for instance, if I recall correctly) and their CDN is top notch IM…

Netlify maintains its own edge network that's actually deployed across various clouds. You are right that Netlify uses AWS lambdas to power Netlify Functions, but that was chosen for the wide support AWS lambda enjoys as a standard. The upcoming edge handlers (in beta) execute javascript directly on Netlify edge nodes worldwide.

Re: Cloudflare Pages: the best way to build JAMstack websites

#64

Post by Animats »

Earwig wrote: post #61
Animats wrote: post #55

Check their terms.[1] First of all, you're giving them a license to your content for their purposes. "By submitting, posting, or publishing your content, suggestions, enhancement requests, recommendations, feedback, information, data, or comments (“Content”) to any Website or Online Service, you are granting Cloudflare a perpetual, irrevocable, worldwide, non-exclusive, royalty-free right and license (with the right…

Crucial definitions: > “Websites” refers to www.cloudflare.com, as well as the other websites that Cloudflare operates and that link to these Terms, and (ii) “Online Services” means Cloudflare’s products and services that are publicly available without a subscription or a Cloudflare account, including, but not limited to, the 1.1.1.1 Public DNS Resolver service, including 1.1.1.1 for Families, Cloudflare Time Service…

Ah, they did make the terms disjoint. Google, in contrast, has overlaps, but the terms for the specific service have priority. "If these terms conflict with the service-specific additional terms, the additional terms will govern for that service."

Cloudflare does force you into arbitration if you buy their services, but at least it's AAA, not JAMS.

Re: Cloudflare Pages: the best way to build JAMstack websites

#65

Post by kmf »

soooe2 wrote: post #23
tyingq wrote: post #17

Earlier quoted context omitted.

Yes, you can...the feature people have been using, which existed before Cloudflare pages is "Workers Sites". https://developers.cloudflare.com/workers/platform/sites

So, the difference here is that pages is free? edit: This offering appears fairly similarly to the paid Workers Sites one. What changed that this is now free?

hey, dev advocate for workers here!

you can definitely do something similar with workers sites.

we recently added workers kv - the storage mechanism behind workers sites - to our free workers tier, so you can host your static sites on workers for free as well.

pages is an evolution of that with better tooling/dx for people who want to get a static site up on our network and want things like deploy previews and pre-configured github integration.

if you want to just have workers do the hosting and want to do all the CI stuff yourself, you can use something like wrangler-action[1] to simplify the process on github actions, or just install wrangler[2] (our CLI) as part of your CI workflow and do `wrangler publish` at the end.

i wrote our github action, so if you decide to go that route, happy to help debug or look over the project to make sure it'll do what you want - i'm @signalnerve on twitter, DMs are open :)

[1] https://github.com/cloudflare/wrangler-action

[2] https://github.com/cloudflare/wrangler

Re: Cloudflare Pages: the best way to build JAMstack websites

#66

Post by tmk1108 »

jshier wrote: post #36

What 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.

I might be getting confused reading their docs but isn't this what you want? https://developers.cloudflare.com/pages/how-to/deploy-anythi...

With optional build command, can't you just leave it empty and then point to the directory that has your HTML files?

Re: Cloudflare Pages: the best way to build JAMstack websites

#67

Post by edaemon »

elithrar wrote: post #51
nrmitchi wrote: post #33

Earlier quoted context omitted.

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…

> "Worker" functionality is already available on both Netlify and Vercel. Workers at those providers do not run _at the edge_ for each request. They lean on AWS Lambda to pre-generate or render assets, but you can't reliably run a function there on every user-facing request without a noticeable latency penalty.

Vercel's functions do run at the edge, but Netlify's are just AWS Lambda functions.

Re: Cloudflare Pages: the best way to build JAMstack websites

#69

Post by rita3ko »

chrisacky wrote: post #68

Cloudflare: Are you planning on making the Docs pages available on Github? They 404 despite having links: https://github.com/cloudflare/pages-docs/blob/master/src/con... My interest is looking at how you do things for the Gatsby node structure.

Sorry about that — had to keep them separate to avoid spoilers ahead of launch, but trying to avoid a migration on launch day.

To satisfy your curiosity though for our Gatsby setup, you can actually check it out here: https://github.com/cloudflare/cloudflare-docs (the rest of our docs are open source and built in the same way, the Pages docs will just go there as a subdirectory, same as the other products).

Doc engine itself is here: https://github.com/cloudflare/cloudflare-docs-engine

Post reply on HN