Migrating to DigitalOcean

Warning: This is not a technical guide. Just a quick note on the decision to migrate all our websites from KnownHost to DigitalOcean.

With this blog as the lab rat, I have started migrating the sites I host to a new server powered by Digital Ocean. It wasn’t a cakewalk but it sure was fun. The decision wasn’t because we were forced to transfer to a new host but because of what I can learn doing so.

For the past years, we’ve been comfortably hosting our websites with traditional VPS (CentOS with LAMP and WHM/CPanel) provided by KnownHost. They’re an awesome company. The servers are fast and reliable, and customer support is superb. I’ve never encountered any big issues with them. The times our websites were offline was all my fault. Hehe.

All thanks to this insatiable itch -- a faulty one, I know -- to break things and learn by building them right back to the old sheen..

Last month at work, we built a server on Amazon Web Services (AWS) for our upcoming website. It includes a setup that we’ve planned for a long time: staging,production and analytics/calculator servers on EC2 instances, backed by MySQL on RDS, and a lot more. It was intriguing...and a little expensive for pet projects like what Issa and I do. Ha!

All the intricacies associated with building this config reminded me of the time I tried setting up a Ghost.org-powered blog on DigitalOcean. Particularly, how it was all configured using the command line.

So last weekend, I spent time learning the basics of DigitalOcean droplets, configuring Ubuntu 14.04 and building a LEMP server inside it. Boy, was it fun!