3 ms·
By linking them I meant using Docker's links feature. http://docs.docker.io/en/latest/use/working_with_links_names/ http://docs.docker.io/en/latest/use/working
by ilaksh 13y ago
By linking them I meant using Docker's links feature. http://docs.docker.io/en/latest/use/working_with_links_names/ http://docs.docker.io/en/latest/use/working_with_links_names...
I have seen people discussing using that link feature where it seemed like they were just setting up a database or something for a single application and then linking that database container. Which seemed like it would be easier to set up the database in the container if possible.
I wasn't saying you can't use Puppet or Chef, just commenting on that particular case with using links for things like database dependencies for a single application.
The use case you describe obviously is not something you would try to manage with Docker alone.
From what you are saying it sounds like you have a good solution.
One thing that I remembered when you mentioned "requirement to run 100s of applications" was this new devops tool called Salt (saltstack.com). I actually don't know much about it but it sounded a little bit like what you are talking about. What do you think of Salt compared to Chef?
- dsissitka 13y agoFor example: https://botbot.me/freenode/docker/msg/5836039/ https://botbot.me/freenode/docker/msg/5836039/
- mateuszf 13y agoOne advantage that I see is for example possibility to upgrade applications server and leave db running. You can then switch to new app-server using nginx making this process transaction like (complete successfully or fail completely).