Live data from Hacker News

How to lose and recover your blog in 30 minutes

antirez.com

11–20 of 33 posts

Re: How to lose and recover your blog in 30 minutes

#11
Pretty fulfilling recovery ? Well done maplebed, lesson learnt and problem resolved.

My least proudest moment quote a while ago was when I realised I just binned a directory I had been writing some code in few files in it, But had them all open in an editor. Recreated the directory and hit save in each tab. phew, disaster avoided

Re: How to lose and recover your blog in 30 minutes

#12
I have lost a couple blogs over the years, mostly out of laziness, letting them expire. I got an itch to write some posts recently and wanted to set up a new site. This time around I decided I would do it with something git friendly, so that I could throw it on github and forget about it if I lost interest. I wrote a "from scratch" site with this in mind and it was working well, so I open sourced the core engine today. It runs on express and is about as bare bones as it gets. http://morganherlocker.com/post/badblog

Re: How to lose and recover your blog in 30 minutes

#13
post #7

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?

this is the blog of the guy that wrote Redis.

Well then that's somewhat acceptable. Somewhat.

Re: How to lose and recover your blog in 30 minutes

#16

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?

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.

Re: How to lose and recover your blog in 30 minutes

#17

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?

> 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?

Re: How to lose and recover your blog in 30 minutes

#20
post #17

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?

> 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?

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