Just use Netlify.
Show HN: Scar – Static websites with HTTPS, a global CDN, and custom domains
31–40 of 171 posts
Re: Show HN: Scar – Static websites with HTTPS, a global CDN, and custom domains
#32Other than the notion that all traffic should be served over HTTPs, if you have purely static site, why the big fuss?
Re: Show HN: Scar – Static websites with HTTPS, a global CDN, and custom domains
#33GitHub 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.
Re: Show HN: Scar – Static websites with HTTPS, a global CDN, and custom domains
#34Other than the notion that all traffic should be served over HTTPs, if you have purely static site, why the big fuss?
Without HTTPs links could be replaced and executable file downloads could be replaced with malware.
Re: Show HN: Scar – Static websites with HTTPS, a global CDN, and custom domains
#35Other than the notion that all traffic should be served over HTTPs, if you have purely static site, why the big fuss?
You can enable HSTS preload and prevent spoofing.
Re: Show HN: Scar – Static websites with HTTPS, a global CDN, and custom domains
#36Other than the notion that all traffic should be served over HTTPs, if you have purely static site, why the big fuss?
people sniffing on what kind of static content you are consuming. think public unsecured wifis or sensitive material.
Re: Show HN: Scar – Static websites with HTTPS, a global CDN, and custom domains
#37Other than the notion that all traffic should be served over HTTPs, if you have purely static site, why the big fuss?
There are plenty of reasons even beyond privacy and MITM content changes. Supposedly HTTPS is better for SEO and also there are browser APIs[1] that only work in HTTPS context
[1]: https://developer.mozilla.org/en-US/docs/Web/Security/Secure...
Re: Show HN: Scar – Static websites with HTTPS, a global CDN, and custom domains
#38GitHub 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.
Re: Show HN: Scar – Static websites with HTTPS, a global CDN, and custom domains
#39This is cool, I'm glad somebody built this! I love netlify but I worry about vendor lock-in.
this doesn't solve vendor lock-in. You're just trading one vendor for another.
Re: Show HN: Scar – Static websites with HTTPS, a global CDN, and custom domains
#40This 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?
Nowhere (unless you use Netlify-specific features like Lambdas, forms etc). You can just copy your static site elsewhere and you're ready.