Live data from Hacker News

Show HN: Scar – Static websites with HTTPS, a global CDN, and custom domains

github.com

11–20 of 171 posts

Re: Show HN: Scar – Static websites with HTTPS, a global CDN, and custom domains

#12
post #10

Nice project. As an aside, I genuinely wonder under which circumstances a CDN will be useful for a static website nowadays. I have a static website that has been on the HN homepage a few times and got picked up by the Chrome mobile recommendations and a nginx/https with slightly tweaked configuration never had a problem handling the traffic even on the smallest DO droplet. Edit: Thanks for these replies.

The CDN makes the site load faster by caching the content on edge nodes close to the client. It’s not for taking load off the origin, but purely for network latency.

Re: Show HN: Scar – Static websites with HTTPS, a global CDN, and custom domains

#15
For anyone looking for a hosted solution, https://surge.sh/ is super nice and simple without any of the complexity of managing the stack yourself. Deploying uses one simple command, and you get hosting and custom domains for free, though I believe SSL is paid for custom domains. (I'm not affiliated with Surge at all, just a happy user.)

Re: Show HN: Scar – Static websites with HTTPS, a global CDN, and custom domains

#16
How much does this cost? I put in some more effort to setup my HAProxy and nginx containers on a Vultr node, but I get LetsEncrypt for free, so I'm just paying for a Vultr node (or DO droplet) and the price of the domain name:

https://github.com/sumdog/bee2

Re: Show HN: Scar – Static websites with HTTPS, a global CDN, and custom domains

#17
post #10

Nice project. As an aside, I genuinely wonder under which circumstances a CDN will be useful for a static website nowadays. I have a static website that has been on the HN homepage a few times and got picked up by the Chrome mobile recommendations and a nginx/https with slightly tweaked configuration never had a problem handling the traffic even on the smallest DO droplet. Edit: Thanks for these replies.

The CDN makes the site load faster by caching the content on edge nodes close to the client. It’s not for taking load off the origin, but purely for network latency.

And by caching it you will reduce traffic to origin.

Re: Show HN: Scar – Static websites with HTTPS, a global CDN, and custom domains

#18

TL;DR this is an AWS stack with 10 AWS services required to build/deploy a static site with HTTPS/CDN I will be staying with netlify

I just built my first static page since middle school this last weekend using netlify and a static site generator [Publii]. I was amazed at how simple and fast netlify is.

I’m confident I could figure out how how to do something much more complicated. But I want to focus on other things and it’s nice to not have to think about it.

Re: Show HN: Scar – Static websites with HTTPS, a global CDN, and custom domains

#19
post #10

Nice project. As an aside, I genuinely wonder under which circumstances a CDN will be useful for a static website nowadays. I have a static website that has been on the HN homepage a few times and got picked up by the Chrome mobile recommendations and a nginx/https with slightly tweaked configuration never had a problem handling the traffic even on the smallest DO droplet. Edit: Thanks for these replies.

What I like about static sites is that you can serve the site in its entirety from a CDN. So you can literally just CNAME www.yoursite.com to yoursite.gitlab.io (or w/e static site host you use). This dramatically cuts down on latency worldwide. It also removes your web server as a single point of failure for short-term outages.
Post reply on HN