Hacker News Reader

Comment by shade23 | Hacker News Reader

Dont want to be a bubble-burster here.This can also be achieved by picking any of the blog engines[1] and hooking it up with a CI. Gives you much more legroom then right?

[1]:https://www.staticgen.com/

View on HN

There's this guide on a "one cent blog"[0] that I've used to create my own website / weblog with a custom domain. It uses Jekyll, CloudFlare and Travis-CI. Probably a bit more work to set up then the tool created by the OP, but also more flexible, I would think. The end result is much the same though. A simple 'git push' is used to publish the blog.

---

[0]: https://hugotunius.se/2016/01/10/the-one-cent-blog.html

I'm the author of "One Cent Blog" thanks for the mention glad it helped you. One interesting difference between the approach described in my blog post(or any other static method) is that you are not relying on a server or a database that can fall over if you get a lot of traffic from say HN. Having static files is a blessing because it scales wonderfully.

The approach in this post relies on maintaining infrastructure, keeping it up to date and patched which for me is a lot of extra work I'd rather not do. Using a standard VPS it's a lot more expensive too.

I do this with jekyll and github but without s3 or travis-ci. I skimmed over the blog but couldn't understand what value s3 adds vs letting github host it. Cloudflare can do the https bits with github directly.

The main value is escaping the constraints on plugins and gems you are able to use with Jekyll on GitHub pages. Don't remember of the top of my head but I believe it's pretty limited.

Reply on news.ycombinator.com