|
I work at a school and am a one-man show with regards to writing various small applications and managing the deployment workflow of said applications. I have been spending the last few weeks learning docker and "trial and erroring" my way through that learning process. I really like the approach Docker takes and I have approached the point where I need to have several containers running, with most of them exposing ports, and some of them needing to link to each other. For reference I have tried to start mapping out my environment:  Can anyone recommend some approaches to managing all of this? Should I just write it all as shell scripts, or maybe use docker-compose?
|
#
¿
Oct 22, 2015 04:47
|
|
|
|
| # ¿ Apr 30, 2024 04:39 |
|
|
minato posted:If it all fits on one machine, just use shell scripts, i.e. a hard-coded startup order, hard-coded ports, etc. You don't need to overcomplicate things with service discovery or multi-host yet. Thanks. Your second point has kinda been ratting around in the back of my head recently, and I think I am going to go with your suggestion.
|
|
#
¿
Oct 22, 2015 06:36
|
|