News for hackers. Stuff that matters.
Re:Bulletproof your blog – survive the Hacker News effect by tikhonj on Sunday December 25, 2011 @07:26PM (#3391905)
He forgot the geekiest option: write your own blogging engine. It's a perfect excuse to use that new language and framework you're learning! Or, if you're not learning anything now, it's a great excuse to start learning.
Re:Bulletproof your blog – survive the Hacker News effect by masnick on Sunday December 25, 2011 @11:53PM (#3392241)
While this is a great learning experience, it is hard to write a blog engine that will stand up to traffic spikes on the first try.

If your goal is learning a new language or framework, this is a great idea. If your goal is to have a reliable, traffic-resistant blog I think it's best to stick with a tried and true platform.

Re:Bulletproof your blog – survive the Hacker News effect by seunosewa on Monday December 26, 2011 @12:53AM (#3392325)
It's not hard. Just write a blog engine that generates static html pages.
Re:Bulletproof your blog – survive the Hacker News effect by masnick on Monday December 26, 2011 @12:58AM (#3392329)
Right, if you write something akin to Jekyll it will work fine.

However, I think most people would probably be trying to learn a framework like Rails or Django if they were writing a blogging engine to learn a new language/framework.

Re:Bulletproof your blog – survive the Hacker News effect by mapleoin on Monday December 26, 2011 @03:50AM (#3392561)
So write your blogging engine as you normally would and then make a button which says: dump to html for each page and then figure out when you want that button to be pressed (i.e. manually or automatically).

More things to learn. Yay!

Re:Bulletproof your blog – survive the Hacker News effect by sunkencity on Monday December 26, 2011 @04:49AM (#3392635)
Build it anyway you like but then wget --mirror before rsync to deploy.
Re:Bulletproof your blog – survive the Hacker News effect by mike-cardwell on Monday December 26, 2011 @07:04AM (#3392768)
Or use caching. My webpages are generated using FastCGI and served by Nginx. So I configured Nginx's FastCGI module to internally cache GET requests for 1 minute.