Local Dev Environments

Docker Compose

These are some of the “lessons learned” by Cloud Posse and general advice for working with Docker Compose.

Fancy Shell Prompts

Fancy shell prompts are not just pretty, they’re also incredibly practical. With the powerline prompt, you’ll always know what branch your working on, if there are any uncommitted changes and the exit code of the last command.


Setting Up “minikube” on OSX Just run… brew install kubectl brew cask install minikube To start minikube, run minikube start Now you should be able to get a list of namespaces: kubectl get namespaces


OSX Dependencies Install Developer Tools The “Developer Tools” package is needed for tools like make and git used throughout our projects. xcode-select –install Example XCode Dialog Install Homebrew Homebrew is arguably the most popular package manager for OSX. Unlike most *NIX operating systems, Darwin does not ship with a package management system. This gap is filled by Homebrew. While other package management systems exist for OSX (e.


Tmate is a way to share a console window or set of console windows. It’s basically a fork of tmux that makes sessions network enabled. It doesn’t matter where the participants are located - inbound firewall rules don’t interfere since it’s all outbound connections.


Vagrant by HashiCorp is responsbile for setting up development environments under VirtualBox. Vagrant handles all configuration management and makes it easy to share development environments by developers.


Dockerfile Best Practices

Use .dockerignore Using a .dockerignore file will rapidly speed up builds by reducing the amount of data copied to the docker VM. Example: .dockerignore **/.terraform .