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?
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?
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.
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.
He was running Redis with persistence turned off by accident. In other words, he used an in-memory database.
Because regenerating the whole site all the time and manually uploading is annoying?