Some time ago, I created an ad-hoc offsite backup solution for a MySQL database after I recovered it. This happened after a client contacted me when one of their legacy databases blew up. The recovery process was quite painful because the backups that they had were corrupted and incomplete (a monthly cronjob). I ended up with a simple setup that used mysqldump, gzip and rsnapshot to great effect. This article talks about effectively using a similar backup method with PostgreSQL.
Today on HN someone posted a small ruby utility to send iMessages via the commandline, which piqued my interest. I would love to send messages to my phone when one of my cronscripts discovers something interesting. However, the utility doesn’t allow sending to self.
So I looked around and found a way to get around this restriction, and it doesn’t even require ruby anymore!
Recently I started on a new side-project: gofinance. It dowloads and stores financial data from the likes of Yahoo Finance, Bloomberg et al. It’s under heavy development but already provides me with a nice way of viewing my stocks from the commandline. A blog post about it is underway but I’m waiting until I can get a bit of security analysis code commited.
Anyway, I felt the need to upload binaries when I got around to tagging a usable release. Normally one would go to github after tagging and pushing, and create the release manually, adding a description and uploading the binaries.
Naturally, being a programmer, I wasn’t content with this repetitive clicking, so I automated the task, and github-release was born.