With everything in one compose.yml, local development becomes rather "heavy", especially with a running ElasticSearch instance. By splitting one docker-compose.yml to a compose.yml (which runs MongoDB and SDX Controller), and a compose.bapm.yml (which runs ElasticSearch and BAPM Server), I'm trying to pare down to a minimal SDX Controller instance for local development.
When we want to start/stop everything, we can still do it like so:
$ docker compose -f compose.yml -f compose.bapm.yml up
$ docker compose -f compose.yml -f compose.bapm.yml down
This changes a couple more things also:
SDX Controller connects to the mongodb service (name provided by Docker networking), and not $MONGO_HOST (the latter is a little more brittle; the former works almost always).
Resolves #204.
With everything in one
compose.yml
, local development becomes rather "heavy", especially with a running ElasticSearch instance. By splitting onedocker-compose.yml
to acompose.yml
(which runs MongoDB and SDX Controller), and acompose.bapm.yml
(which runs ElasticSearch and BAPM Server), I'm trying to pare down to a minimal SDX Controller instance for local development.When we want to start/stop everything, we can still do it like so:
This changes a couple more things also:
mongodb
service (name provided by Docker networking), and not$MONGO_HOST
(the latter is a little more brittle; the former works almost always).