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

Netlify Dev

netlify.com

Post reply on HN
Print view View original

201–210 of 237 posts

Re: Netlify Dev

#201

Post by thatssosid »

poxrud wrote: post #175
thatssosid wrote: post #171

I recently moved my site[0] from WordPress to Netlify Used HUGO and then one of my Post regarding MacBook Thermals was trending on HN, The site had more than 12K visitors. If I had been using WordPress I could only imagine how catastrophic that would be. Though I crossed their 100GB limit. But since this was a rare spike in traffic I feel their free plan is very generous. Netlify+ static site generators is good alter…

With proper caching even a $5 DO droplet would be easily able to handle this load. With caching + cdn you should be able to handle virtually any load. I personally run cloudfront in front of all of my WP sites, even the low traffic ones because the costs are negligible.

I agree that DO would handle the load. The con is that it costs 5$+tax. Where as netlify is free and CDN and caching is taken care by netlify. Saves time

Re: Netlify Dev

#202

Post by SiVal »

PudgePacket wrote: post #194
SiVal wrote: post #186

Earlier quoted context omitted.

Obvious to everyone except me, it seems, so obvious that it's never mentioned by anybody, is: What about databases? The answer could be, "Well, obviously, it's not for database-backed websites", or "Obviously it's perfect for database-backed websites, because now you can use their X feature for your database", or "Obviously, you use some other company to host your database but Netlify for everything else, which is a…

Honestly? Most internet sites don't _need_ a database. You could probably replace most* wordpress/squarespace/wix sites with a statically generated site. You can call api's from JS and host your database separately, also possible that people use some kind of "serverless" database like google firebase.

Most internet sites don't _need_ a database.

Right, and the rest of them—a very significant portion—do. And yes, I realize that it's possible to use JS to fetch from anywhere, but what I'm wondering is what people are thinking when talking about Netlify.

Are they thinking that this isn't really for database-backed websites but can be used if some other Netlify advantage justifies putting your database and the server code that uses it in different timezones? Or is it the opposite, that this is actually a better way of managing a database-backed website?

What is the positioning of this new type of managed hosting with respect to websites that depend on databases full of, say, customer data? It seems as though that would be a FAQ, not an exotic niche.

Re: Netlify Dev

#203

Post by lloeki »

pkd wrote: post #196
bastawhiz wrote: post #185

Earlier quoted context omitted.

You're forced to use Jekyll, though, and you're forced to use Github. Netlify lets you generate your site however you want and doesn't tie you to a git provider.

You're not forced to use Jekyll. You just get some nice things if you do. As long as you have a pages repo with an index.html in the root, GitHub can serve it for you. How you generate the repo is completely up to you. I have my own custom static site generator that I use to publish my blog, I use that with a script that does some git dance to keep things clean and it just works.

If you don't use Jekyll (let's say, e.g Hugo) you have to commit the content/artefacts to be published to the repo. Committing artefacts to a repo, even if it's a dedicated branch with a separate root, always seemed like a glorious hack to me with consequences such as CI needing push access to the repo. GitLab CI+Pages doesn't need such a hack but then, competing with that would mean GitHub would basically have to allow running arbitrary process during the publish pipeline, which means they'd enter CI space.

Re: Netlify Dev

#204

Post by dasil003 »

Touche wrote: post #31

Can anyone explain the elevator pitch of Netlify to me? I know it's become quite popular in the last couple of years and I can't figure out why. I don't doubt that it's good at what it does, but it seems to do the same thing as any number of services. For example, I see a lot of people talk about it for static sites. But you get free static sites through GitHub, nearly free static sites on Amazon S3. What does Netlif…

Github Pages or Amazon S3 are good tools, with a few features that may or may not suit your use-case, but in practice it's pretty easy to find one small detail that ends up being a dealbreaker (eg. you want to use Jekyll but you can't run custom plugins).

Netlify by contrast has the vibe of a swiss army knife or maybe a unix shell: a lot of very sharp tools that you can use to set up static sites in a lot of different ways and that compose nicely. I haven't done a ton with it, but you just get the feeling of a high power to weight ratio.

Re: Netlify Dev

#205

Post by jpincheira »

We use Netlify for https://standups.io and we still are not paying a penny for their service. It works for our different environments, creates deploy previews out of every branch, supports split testing, and we even use it as a CI for our ReactJS app using Cypress! It's so painless and reliable, we just love it.

Re: Netlify Dev

#206

Post by dsumenkovic »

davchana wrote: post #180
brianpgordon wrote: post #167

Earlier quoted context omitted.

If you're not aware, you get most of that for free with GitHub pages: https://pages.github.com/ It deploys when you push, is based on Jekyll, and GitHub handles all of the hosting/HTTPS/caching themselves.

Gitlab too does this, along with free unlimited private repos & published static sites; html n Jekyll n all. Just a happy user.

Glad to hear that you enjoy using GitLab! Here's a link if anyone wondered https://about.gitlab.com/product/pages/

Re: Netlify Dev

#207

Post by madeofpalk »

tkjef wrote: post #172
madeofpalk wrote: post #146

Earlier quoted context omitted.

> But you get free static sites through GitHub GitHub doesn't support a build process, right? So you would have to do that yourself and commit that. > nearly free static sites on Amazon S3 You'll have to manage the build and deploy here yourself then. Netlify is great because its easy, and free (if you're under their bandwidth cap). They have really cool features like automatically deploying a preview environment for…

for Amazon S3 i setup the s3, cloudfront & cert manually (should put it in terraform, but it takes just a second). here's a nice article to walk you through that (says it's for hugo, but you could use it for any ssg): https://agop.me/post/https-enabled-portfolio-hugo-s3-cloudfr... then i build and deploy with a bash tool i made called NanoCD: https://github.com/tkjef/NanoCD has lots of helpful options. easy to wrap y…

or use netlify.

the whole point is that I don't want to futz around and use terraform, or read a tutorial, or build a bash tool or whatever.

It's literally like 3 clicks in Netlify and it'll handle _everything_ for me. I point my DNS to Netlify and then I've got HTTPS for free as well.

I used to deploy to S3 as well, and I had a small little `yarn deploy` script that did the webpack build and upload to S3 - its not that hard https://github.com/joshhunt/destinySets/blob/ae08807e3d23de9.... But Netlify is so much easier, especially when working from multiple machines.

Re: Netlify Dev

#208

Post by madeofpalk »

brianpgordon wrote: post #169
madeofpalk wrote: post #146

Earlier quoted context omitted.

> But you get free static sites through GitHub GitHub doesn't support a build process, right? So you would have to do that yourself and commit that. > nearly free static sites on Amazon S3 You'll have to manage the build and deploy here yourself then. Netlify is great because its easy, and free (if you're under their bandwidth cap). They have really cool features like automatically deploying a preview environment for…

> GitHub doesn't support a build process, right? So you would have to do that yourself and commit that. GitHub builds your site with Jekyll.

I don't use Jekyll.

Re: Netlify Dev

#209

Post by qfarhan »

mattfrommars wrote: post #178
icebraining wrote: post #148

Earlier quoted context omitted.

Yes, but here you don't need to manage a Jenkins installation.

Right. But in this system, I'll need to manage Netlify.

To be honest, there is nothing to manage in Netlify. Just first time connect the git repo during sign up procedure. Additional benefits (at least for starter) are 1 click SSL management. They also provide functions and form, but I have not used them so not aware of how useful they are. :)

Sure they are not a huge improvement compared to your setup. But streamlining the procedure for someone not familiar with the pipeline is a great benefit.

Re: Netlify Dev

#210

Post by kaishiro »

soonoutoftime wrote: post #200
pkalinowski wrote: post #153

Netlify is amazing: 1. Free 2. Good support 3. Custom domains with SSL 4. Takes care of most important backend stuff (forms and webhooks) 5. Functions (Lambda with zero config needed) 6. Abstracts server stuff like [redirects]( https://www.netlify.com/docs/redirects/ ) Lambda and redirects are the best. I can just put my scripts in a folder and they automagically work. In my LinkedIn profile my website address is not…

> 1. Free ... 4. Takes care of most important backend stuff (forms and webhooks) From my reading of https://www.netlify.com/pricing/#forms you will need to pay $19/month/site (!) just to collect the data from 1000 form submissions. By the time you have a couple of sites like this the price is already way too much for me and anyone else with basic backend knowledge. I hope I've misunderstood.

To be fair, you get 100 submissions/month for free. And since you get drop in honeypots and reCAPTCHA those are typically valid submissions.
Post reply on HN