[HorizonXP]

And a blog requires a Redis back-end because?

I've hosted my blog on S3 & CloudFront for a while now without issue. Comments are hosted by Disqus, and the static files are generated using Pelican.

Seriously, unless you're using your blog as a massive CMS, why not use static files?

[zemo]

this is the blog of the guy that wrote Redis.

[HorizonXP]

Well then that's somewhat acceptable. Somewhat.

[gamache]

Oh, admit it. Antirez wrote a hell of a blogging platform.

[onli]

Because "comments are hosted by disqus" is just not acceptable for every blog, and every project. And if you already store comments in a database, you might as well store the entry itself.

And if you do that, you might as well build a real blog with an editor integrated. And the ability to upload images. And the ability to edit entries and comments on the blog itself. Oh, and having comments, ping- and trackbacks in the database, how about using a bayesian spamfilter?

And no, this is not a massive CMS.

[qznc]

"oh, static systems are for people that don't have fast databases ;-)" -- antirez (article author) https://twitter.com/antirez/status/407184116275503104

[oinksoft]

Agreed, I'm moving my small website to a bash static generator right now. But I'm not so sure about hosting comments with somebody like Disqus. Better to host and moderate them yourself, or skip them altogether.

You could do a lot worse than Redis for a blog's data store though. It's simple, fast, persistent, and easy to set up.

It's weird that the author lost his blog data from a reboot. Maybe he lost his Linode? It a bummer that he didn't have a recent backup of the redis database. Recovering a blog from Google's web cache doesn't sound like fun.

[kijin]

> Maybe he lost his Linode? It a bummer that he didn't have a recent backup of the redis database.

He was running Redis with persistence turned off by accident. In other words, he used an in-memory database.

[swah]

Why? There are mature databases, mature frameworks. Static files is pretty limited... if you mean that the blogging system wrote the static files and nginx served them, them I'd agree.

[chc]

> Seriously, unless you're using your blog as a massive CMS, why not use static files?

Because regenerating the whole site all the time and manually uploading is annoying?

[autotravis]

because `./build.py; rsync -r site/ site.com:~/site/` is easy?