James Scott

3 minute read

New Blog, New Server

My Wordpress blog is long gone! Hello, Hugo! This post is the beginning. This will be one part of the series that describe my new deployment onto DigitalOcean. Still working out some kinks but rather document what I have while it’s still fresh.

Back Story

Previous to using DigitalOcean, I used InMotion Hosting. In particular, I used their Power Plan. The plan was just a shared hosting plan with a bunch one-click apps. The only bad thing was, I didn’t really have a use for those other apps besides Wordpress. Also, I couldn’t use Let’s Encrypt for free certs. Finally, my subscription was up at the end of August and I received a notice of renewal for $200+ for a two year extension. (The first time I paid for it, it was not as much because of a promotion either.) Thus, I figured, I needed to move.

Plan

Update Here’s the repository for this plan in action!

For Infrastructure: DigitalOcean

  • More control than what I had before.
  • At the time, there was a way to get $35 of credit.
    1. Use someone’s referral code like mine to get $10.
    2. Create a CodeAnywhere account. Upon creating an account there, you will see a Connection Wizard and there will be an option for DigitalOcean. After clicking there, you will see an option for getting a promo code.
    3. Both of the codes will not work, upon signing up. You will need to submit a ticket for the other. DigitalOcean’s support is really helpful and quick to add the other code to your account.

For infrastructure management: Terraform

  • I really love the idea as infrastructure-as-code and Hashicorp’s Terrafrom tool is something I have been wanting to dive into more.
  • I want to be able to provision everything and tear everything down at the drop of a dime with a single command.
  • When I say provision, I mean to create the droplet, to secure it, to configure my domains, and to deploy my apps and databases (include backups).
  • When I say tear down, I mean to backup the databases, to remove the apps, to and destroy the droplet.

For deploying apps: Dokku

Dokku is a Platform as a Service (PaaS) for a single node. A PaaS makes it easy to deploy apps by removing the burden of having to configure the infrastructure for every app. Theoretically, it allows you to easily scale as well (Dokku is a slightly different case).

Pros of Dokku:

  • Simple to setup
  • Can run on one droplet (less money than running a real platform as a service)
  • Nice plugins (e.g. Let’s Encrypt for SSL certs for all the apps.)
  • Can easily deploy any toy apps I have.

Cons of Dokku:

  • Not really scalable since it’s only limited to one node.
    • But, I don’t need more than one node right now.

I looked at alternative PaaSs and also Orchestrators.

Kubernetes: The Container Orchestrator aka k8s

  • This is where all the buzz is at. I wanted to do this.
  • Too expensive to setup for my needs.
    • Need multiple droplets to ensure high availability and for the number of components.
  • DigitalOcean has no official instructions on how to do this.
    • People in the community have done this but found it dated or incomplete.

Flynn

  • Minimum infrastructure needs are similar to Kubernetes, which brings about cost.

Deis

  • v2 uses Kubernetes. See notes on Kubernetes.

Next Steps

I will be making a blog post series about this whole process. More to come. Stay tuned!!

comments powered by Disqus