discoverd, router: Use SO_REUSEPORT.

Signed-off-by: Blaž Hrastnik <blaz.hrast@gmail.com>
all: Update Godeps to include go_reuseport.

Signed-off-by: Blaž Hrastnik <blaz.hrast@gmail.com>
controller, bootstrap: Pass through the HostNetwork option.

Signed-off-by: Blaž Hrastnik <blaz.hrast@gmail.com>
router: The router listeners themselves should be reusable too.

Signed-off-by: Blaž Hrastnik <blaz.hrast@gmail.com>
all: Bump Go to 1.4rc2

Signed-off-by: Jonathan Rudenberg <jonathan@titanous.com>
blobstore: register when fs storage is used.

Signed-off-by: Michael Elsdörfer <michael@elsdoerfer.com>
test: Log when removing rootfs

Signed-off-by: Lewis Marshall <lewis@lmars.net>
test: Fix builds.js

Signed-off-by: Lewis Marshall <lewis@lmars.net>
Merge pull request #544 from flynn/test-runner-rootfs-cleanup

test: Log when removing rootfs
Merge pull request #543 from miracle2k/blogstore-register

blobstore: register when fs storage is used.
Added environment support to the install buildpack process

- If a custom buildpack is being used chances are it's because there is something unique about the environment
- The most standard annoyance in enterprise environments is the lack of direct outbound connectivity
- Proxy support needs to be propogated during the entire end to end build process.
- http_proxy and https_proxy can be added as environment variables
- Custom buildpacks can use the environment variables to be proxy aware
- install-buildpack is now proxy aware; it simply loads the environment variables from ENV_DIR
Added ENV_DIR and Proxy support

git will pick up https_proxy and http_proxy if set and use those for the clone
Removed comment
Fixed variable escaping for $env_var
Merge pull request #541 from flynn/so-reuseport

SO_REUSEPORT
Restrict environment variables loaded

- Restrict to just proxt related environment variables
- Support upper and lowercase form
Removed whitespace
Merge pull request #550 from flynn/go1.4rc2

all: Bump Go to 1.4rc2
Vagrantfile: Fix escaping of environment variables in dev vm bashrc initialization.

Previously, the hardcoded $PATH was ending up in the bashrc file.  The "$PATH" variable is now placed in the bashrc file, thus doing the more correct thing with chaining changes to that variable.

Signed-off-by: Eric Myhre <eric@flynn.io>
Merge pull request #553 from flynn/fix-vm-env-template-escaping

Vagrantfile: Fix escaping of environment variables in dev vm bashrc initialization