Local Development With Docker

This is part 1/2 on development with Docker. In this article, I'll be covering how and why you should be using Docker in development. In the next one, I'll cover production deployments.

Why?

When building a typical project at work, I need a few things. Node, a bunch of node modules (npm), and maybe more than that down the road. If someone on the team needs to make a change to my codebase that usually works on a different area of our tech stack, they tend to get annoyed at the setup process. Maybe they are on an outdated version of node, need to npm install because they haven't ran the repo in so long, or some other dependency was introduced. This can be frustrating when all you want to do is code, not worry about environment setup. It doesn't matter what your tech stack is, Docker can get rid of all of the problems you have. So why should you follow this post? Because none of these things will be problems ever again.

Setup

I'm on a Mac, and thankfully Docker support has gotten a lot bette…