made an RDS instance a replication slave of our database hosted with Linode
fiddled with my bash prompt and other .bash_profile goodies
made breakfasts and lunches for my 2 little kids
made myself a lovely salad for lunch
dropped my kids at school (bigger task than it sounds like)
gone to work, where I
held scrum
reviewed and merged pull requests
reviewed and rejected pull requests
finished a bug fix
reverted a major feature deployment
communicated a plan to migrate our database off of Linode and into RDS
debugged and tested our database migration plan
went to a meetup
fixed my home printer not printing
plunged a toilet
cleaned a toilet
written this blog post
Still to do:Update: Also Done
review and script our migration plan
migrate our database off of Linode and into RDS
3 comments
I have chivers when I think of the time when we’ll move off of Linode… I fear that our MySQL replication “accross” the web will be quite flaky given the volume of transactions 🙁
I had been pretty apprehensive, too. But Linode just forced our hand with this downtime. AWS has the same security issue to deal with, but no downtime.
I have chivers when I think of the time when we’ll move off of Linode… I fear that our MySQL replication “accross” the web will be quite flaky given the volume of transactions 🙁
I had been pretty apprehensive, too. But Linode just forced our hand with this downtime. AWS has the same security issue to deal with, but no downtime.
dang those printers…