How to lose and recover your blog in 30 minutes
1–10 of 33 posts
Re: How to lose and recover your blog in 30 minutes
#2It's funny, for all the work that goes into some things simpler is so often better. I've had a lot of value out of the content antirez has posted on his blog - all along it was just a block of unformatted text.
Re: How to lose and recover your blog in 30 minutes
#3If the comments are outsourced then why have a backend at all? Just pop all of the posts into an S3 bucket and update the index when creating a new one. No server needed.
Re: How to lose and recover your blog in 30 minutes
#4If the comments are outsourced then why have a backend at all? Just pop all of the posts into an S3 bucket and update the index when creating a new one. No server needed.
Dogfooding his own project I would assume.
Re: How to lose and recover your blog in 30 minutes
#5Damn... After I think I've got all the knobs set "just right", I'll always reboot just to see what happens.
This usually catches various common problems not quite as serious as this one... daemon doesn't start, kernel panics, more updates required after boot, etc.
The last time I had something like this happen, needing to restore from a weekly backup, Google or Archive.org had already cached everything new and I was able to recover it all without much hassle.
Re: How to lose and recover your blog in 30 minutes
#6And 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?
Re: How to lose and recover your blog in 30 minutes
#7And 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.
Re: How to lose and recover your blog in 30 minutes
#8Funnily enough, just yesterday a friend of mine just told me that a few years ago the database of a blog community he runs got corrupted and had to be recovered. Unfortunately, the server where he was sending his backups got full like 3 months prior and he didn't know, so he had basically lost 3 months of data. He recovered most posts checking Google Cache too. And yes, now he has all the systems properly set up with alerts, proper backups and such :)
Re: How to lose and recover your blog in 30 minutes
#9[deleted]
Re: How to lose and recover your blog in 30 minutes
#10So really ... google cache to the rescue...