Hacker News Reader

Comment by fizzbatter | Hacker News Reader

Hmm, i have a bunch of static sites on custom domains through things like Github pages. Guess i need to get them figured out.

View on HN

Have a look at Netlify (https://www.netlify.com) - our free tier is like GitHub pages on steroids including HTTPS for custom domains (and deploy previews, use any build tool not just Jekyll, redirect rules, etc...).

what do you mean when you say "not just jekyll"?

We have a Metalsmith static site that requires "npm build" to build and Netlify seemed to figure it out automatically. Pulls directly from GitHub, built, deployed, SSL with LetsEncrypt. All for free.

Very nice service.

GitHub Pages only supports building sites with Jekyll[0].

According to the Netlify documentation[1], it looks like they support any/most tools, including Jekyll, Grunt, Middleman, Roots, Hugo, etc.

[0]: https://help.github.com/articles/using-jekyll-as-a-static-si...

[1]: https://www.netlify.com/docs/continuous-deployment

I host my static sites out of S3 and use Route53 to manage my DNS. If you go this route, it's only a few clicks through a setup wizard to get an SSL cert and enable https.

I use CloudFlare with SSL (Full) for this. Not optimal, but according to a recent comment on HN (https://news.ycombinator.com/item?id=12389850) CloudFlare plan to offer "more granular origin certificate validation" in the future.

"Don't let the perfect be the enemy of the good". While not the optimal solution this route significantly increases security while at the same time being easy and free to setup. I hope that CF starts to validate github pages certs so we can switch to their "strict" option in the future.

Reply on news.ycombinator.com