Closed klingerf closed 8 years ago
I like this, except promoting scribe, as we really want that to die.
@adriancole Thanks for the feedback. I that case would it make sense to just remove the collector container entirely from both docker-compose.yml and docker-compose-mysql.yml? As it is now, it feels a bit incongruous for the collector to show up in one place but not the other.
Other thoughts -- maybe we should just remove docker-compose-mysql.yml, in favor of better documentation on running each of the provided containers? Am happy to put together some documentation in a separate branch if we want to go that route.
I think mysql should be advertised as it was added because more people know that vs cassandra. I don't object to removing collector from both places. These files are supposed to be a quick start anyway, vs an actual recommended topology.
Ok, great, have updated this branch to remove the collector container from the docker-compose files. And am cross-posting my comment from the openzipkin gitter transcript.
i’d like to:
note after step 1 we’ll need to publish new docker images, since it will be much easier to remove linking once we have a new image that includes this change: https://github.com/openzipkin/docker-zipkin/pull/91/files#diff-3cf38cad5817677135b052c2d9c36ce0R7
nice work
The docker-compose-mysql.yml file appears to be incomplete, as it is not running the collector container. This branch switches that configuration to be an extention of the default docker-compose.yml file, using docker-compose overrides, described here:
https://docs.docker.com/compose/extends/#multiple-compose-files
In addition, I've fixed an issue where the zipkin-cassandra container would not exit if the storage type was not configured correctly. And I've modified the zipkin-web container to allow overriding the query service address without requiring linking.