$ brew install docker

$ brew install docker-machine

$ docker-machine create --driver=virtualbox default

eval "$(docker-machine env default)"

$ brew install go

  $ brew install jq
  ```

3. Install kubectl

## Pre-requisites for build server

1. Docker should be installed

2. Create a job

## Makefile

The following basic commands are available. They need all the pre-requisites
for development to be installed in order to work.

* `build`: This is the default rule. Will build your app
* `utest`: Runs the unit tests
* `itest`: Restarts and runs the integration tests
* `itest.env`: Restarts the integration test environment on Kubernetes
* `itest.run`: Runs the integration tests
* `ibench`: Restarts and runs the integration benchmarks
* `ibench.env`: Restarts the integration test environment on Kubernetes
* `ibench.run`: Restarts and runs the integration benchmarks

The following commands run in docker. They can be used with only docker
installed.

* `deploy`: Build rule for Jenkins to build, test and publish the app
* `dist`: Builds all the docker images
* `distrun`: Runs the application using the images generated by `dist` in docker
* `distrun.env`: Like `distrun`, except it runs the `env` command. This lets you
  verify if your secrets made it into the config file.
* `distrun.sh`: Like `distrun`, except it runs the shell. This lets you
  inspect your image. Not that if you image does not have the `sh` executable,
  then you won't be able to shell in.
* `distbuild`: Runs `build` in docker. This allows for builds on machines with
just docker installed; so no need for golang.
* `distpush`: Pushes the commit-tagged docker images
* `distpublish`: Pushes the release- and latest- tagged docker images
* `distutest`: Runs the unit tests in docker. This will also start a test
database image and connect your run to that.
* `distitest`: Runs the integration tests in docker. This is the same as
running `itest`. The difference is that you don't need to install Kubernetes
locally. If you want your Kubernetes to apply in the image, you need to
set `KUBERNETES_CONFIG`.
* `distitest.env`: `itest.env` run in docker
* `distitest.run`: `itest.run` run in docker
* `distibench`: Runs the benchmark tests in docker
* `distibench.env`: `ibench.env` run in docker
* `distibench.run`: `ibench.run` run in docker

The following are extra commands that you may find helpful.

* `fmt`: Runs `go fmt` on your Go packages
* `devconsole`: Enters the container image. Useful for starting kubernetes or running delve.

## Overview of structure

## Upgrading bedrock

To upgrade your bedrock, you would:

Then you can re-generate the stubs. If you commit your existing changes before
re-generating, then you can see the differences that were made, and you would
have a change to reconcile the differences.