use docker network to avoid --link and more. #751
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Hello,
I've started to modified mupx (starting from the v1.5.3 tag) to use a docker bridge network to inter-connect mup application containers and mongodb container.
A "mupnet" network is first created (install-docker.sh)
Then each container is started with --net=mupnet (no more --link in the useLocalMongo case) so each container knows others by name automatically (through a dynamically computed /etc/hosts).
I've not yet looked for the ssl frontend container, but have an idea. Tell me what you think about it :
The goal could be to have only one frontend container, common to all app containers which is automatically reconfigured with a new vhost when new meteor containers are created/started (using docker events and a small script). The frontend can handle ssl and no-ssl and proxy named vhost toward meteor containers (as there are in the same docker net).
Anthony.