initial commit. fully operational
some fixes, mostly to the readme
readme editing
minimize route statefulness
grammar and such
succinct and accurate
get specific on size
docker listener utility to reproduce weird event listener behavior
missed some error checking, and added a workaround to weird docker event listening bug
remove workaround for https://github.com/fsouza/go-dockerclient/issues/101
Merge pull request #7 from jbergknoff/jonathan

Fix duplicate logging
use DOCKER_HOST to connect to remote socket

The Docker client respects DOCKER_HOST to set the -H flag for the
client. Using the same envvar makes it easier for development on
platforms like OSX where DOCKER_HOST is recommended to connect to
boot2docker.

Signed-off-by: Matthew Fisher <matthewf@opdemand.com>
Commit logspout binary to repository; update Dockerfile reference and Makefile

Updated Makefile:
 - to have a stage/logspout target which copies the build output to the stage directory
 - to depend upon the stage/logspout when building the container
 - to force the OS/ARCH to be linux/amd64 (prevent Mac users from destroying the world)

Updated Dockerfile:
 - ADDs from the stage location
Merge pull request #16 from KoanHealth/master

Commit logspout binary to repository; update Dockerfile reference and Ma...
fix(controller): work around fleet state reporting on deis run
fix(controller): bump timeout to 20 min for image to download
Merge pull request #1978 from gabrtv/fix-deis-run

fix(controller): work around fleet state reporting on deis run
ref(scheduler): introduce deis/publisher

In Deis's scheduler abstraction, we run a "sidecar" systemd unit which
publishes the running host and port of the application to etcd for
service discovery.

The issues with this sidecar container are as follows:

- it must live on the same host as the container
- it must wait for the container to come up before publishing
- it relies on using the docker client directly

The last point is crucial. This means that we are effectively
monitoring the docker client for container uptime, which is not the
same as monitoring the container directly.

This has been refactored into a micro-service image called
deis/publisher. Publisher listens directly to a docker socket
bind-mounted into the container and listens to the docker events API
for running containers. Running containers that follow the same format
as our current naming scheme (e.g. hardy-woodsman_v2.web.1) are
published to etcd for service discovery. This allows us to remove the
hard dependency on running a sidecar container to publish the app
container to etcd. Instead, one container per host publishes all
apps running on that host.

MIGRATING: to migrate to this change from existing hosts, you can run
the following:

    ><> # rsync publisher/systemd/deis-publisher.service to every node
    ><> for i in deis-1.example.com deis-2.example.com; do ssh core@$i -c "sudo systemctl enable /home/core/deis-publisher.service && sudo systemctl start /home/core/deis-publisher"

Then, you'll want to remove each announce sidecar attached to the applications:

    ><> fleetctl destroy <appname>-_<version>.<proctype>.<conatiner ID>-announce
feat(deisctl): add deis/publisher

With this change comes the introduction of the ability to add global
units to the project. Before, we would always prepend "@1" to the units
because we always assumed they'd be scalable. This is not the case for
global units, so I reverted that behaviour.
fix(publisher): use git sha tag for `make build`