…s exposed would cause services to overwrite each other

Synchronize etcd cluster in registrator on service registration.

…protocol-fix

Missing protocol fix

Checks for new versions with the "usage" service and automatically displays a
standard version message when the "--version" flag is passed.

Add new version checker

Signed-off-by: Marcelo Salazar R <chelosalazar@gmail.com>

Signed-off-by: Marcelo Salazar R <chelosalazar@gmail.com>

go 1.4 is now required (miekg/dns#197)

Upgrade to alpine:3.2 and go 1.4

bridge.New no longer attempts to ping an adapter, caller must now use the bridge Ping method.

A few simple tests have been added to the bridge pkg

Refactor bridge for better testability

Conflicts:
	bridge/bridge.go

Retries to backend in the startup

Synchornize etcd cluster in registrator on service registration

…s-named-service

Fix multiple ports named service

Instead of using the "kill" and "stop" events, this uses the exit status to
check whether the container was terminated via a signal. This will be more
reliable since the "kill" event can also be sent for non-fatal signals such as
SIGHUP.

Fixes gliderlabs#248

Fix releases link in README

Go's "flag" module only parses options up until the first non-option argument,
so additional arguments are left unparsed in "flag.Args()". We only expect one
argument, but additional arguments were ignored, leading to some confusion
about options that were ignored.

This updates the Usage() message with the syntax showing the options before the
registry URI, as well as more detail if the registry argument is missing, or
additional arguments are found.

When a service was previously registered into the service registry
and registrator exits without unregistering, registrator now queries
the backend to see which services were registered, and checks against
it's internal list to determine which should be unregistered.

Align SPONSORS text

Cleanup dangling services - rebase

When using the Docker multi-host networking, IPAddress under NetworkSettings is set to an empty string and the container IP can be retrieved from NetworkSettings.Networks.

At this point it is assumed a single Docker network is associated with the container

This is a cherry-picked commit to fix the merge history.

Add more detailed usage regarding options placement

Support for Docker multi host networking

Fix specific port names not overriding port suffix

Initial basic zookeeper backend for registrator

Small docs refurbishment

Note for ignoring individual service on container

Add support for Consul unix sockets

…nning

Use exit status to determine if container was killed

  add support hostip for overlay network

…base

gofmt bridge/

Fix missing ServiceAddress when using networks from docker-compose (overlay)

Default etcd backend port to 2379

added Consul TCP Health Check

Closes gliderlabs#290

Fix gliderlabs#365

…llow publishing services if the base service path already exists, and allow publishing into the root of zookeeper. (gliderlabs#367)

adding TLS support for consul backend

add support for consul https health checks

Closes gliderlabs#449

Add caution note on resync parameter

…iners

Remove stale services from registrator

- add cleanup parameter in the doc
- alphabetically reorder the parameters list

Add cleanup parameter in the doc

Add consul initial check status to service attributes

document how to run when consul uses and acl

Fixes registrator to follow the following documentation.
http://gliderlabs.com/registrator/latest/user/services/#service-name

Fixes logic for appending port to SERVICE_NAME

Use ExposedPorts for --net=host