Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

How to lose and recover your blog in 30 minutes

antirez.com

Post reply on HN
Print view View original

21–30 of 33 posts

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

#21

Post by kijin »

oinksoft wrote: post #16
HorizonXP wrote: post #6

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…

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

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

#22

Post by kijin »

The Wayback Machine has numerous caches of his website, dating back over 7 years. This should be good enough to restore all the timestamps to within 24 hours of their original values, as well as catch anything that Google's cache might have missed.

https://web.archive.org/web/*/http://antirez.com

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

#24

Post by onli »

HorizonXP wrote: post #6

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?

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.

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

#25

Post by antirez »

kijin wrote: post #22

The Wayback Machine has numerous caches of his website, dating back over 7 years. This should be good enough to restore all the timestamps to within 24 hours of their original values, as well as catch anything that Google's cache might have missed. https://web.archive.org/web/*/http://antirez.com

That is helpful, thanks! I'll recover the dates...

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

#26

Post by swah »

HorizonXP wrote: post #6

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?

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.

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

#27

Post by jheriko »

"simple systems are really better than complex systems when something bad happens"

isn't that super ironic? that by configuring something in a stupidly elaborate way you had a problem...

redis may be super stable but cosmic ray neutrons are a thing and they will screw you one day eventually. :)

surely the real saviour here is the internet and its ability to keep crusty old data alive for you through caching and such...

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

#30

Post by qznc »

auxbuss wrote: post #29
borplk wrote: post #28

I'm surprised he isn't using a static website

Salvatore (antirez) had a nice pithy response to that: oh, static systems are for people that don't have fast databases ;-) https://twitter.com/antirez/status/407184116275503104

My database is called ext4. It is plenty fast for a blog. :-)
Post reply on HN