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

Post by codegladiator » Wed, May 22, 2019, 5:00 PM UTC

mevile wrote: post #49

NateEag wrote: post #47

Am I the only one who still hosts my own static sites on a plain old virtual machine? It's pretty simple to configure nginx for static sites, and by doing it yourself you reduce vendor lockin to just about nil. Even if S3 is massively cheaper, $5/month for a tiny VM seems like a small price to pay for being vendor-abstract. I suppose S3 is way less likely to suffer a meaningful outage than my little VM, but how many…

> you reduce vendor lockin I don't know why anyone cares about vendor lock in. It's either trivial to move an aws lambda to a google cloud function because you don't have a lot going on, or it's not trivial to move stuff from even your own servers to other servers because it's under huge load and you have considerable amount of data you'd have to migrate under complex conditions. Moving around is either hard or easy…

Post by nkellenicki » Wed, May 22, 2019, 5:09 PM UTC

gtirloni wrote: post #38

jaden wrote: post #6

GitHub pages [0] gives you static sites with HTTPS and a custom domain without nearly as much complexity as this if you're looking for an alternative to Netlify. [0] https://pages.github.com/

I feel like Netlify has set the standard in this area now so I'm curious to learn what's different when I see these projects mentioned here.

Post by ainiriand » Wed, May 22, 2019, 5:22 PM UTC

jkarneges wrote: post #33

jaden wrote: post #6

GitHub pages [0] gives you static sites with HTTPS and a custom domain without nearly as much complexity as this if you're looking for an alternative to Netlify. [0] https://pages.github.com/

It even gives you a CDN. GitHub Pages is fronted by Fastly.

Post by acdha » Wed, May 22, 2019, 5:40 PM UTC

dvfjsdhgfv wrote: post #43

zachruss92 wrote: post #19

Earlier quoted context omitted.

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.

> you can literally just CNAME www.yoursite.com to yoursite.gitlab.io After so many years I still can't really understand how easily people hand over almost complete control over their site to someone else, just because everyone else does. It's like handing over your e-mail account passwords when LinkedIn started. Yes, CloudFlare, Google and others are helping you, but there is a price to pay that might not be immedi…

Post by paulgb » Wed, May 22, 2019, 5:52 PM UTC

reificator wrote: post #27

paulgb wrote: post #2

This is cool, I'm glad somebody built this! I love netlify but I worry about vendor lock-in.

I'm usually paranoid about vendor lock in, but I can't join you on this one. Netlify assumes a version control repository that you can pull from, run a build step, and then host static files from. The build tools are open source, the output is static and trivial to download and rehost, and the repository is git meaning one clone is all you need to port to any other service. Where exactly is the vendor lock in?