etienne-napoleone
commented
6 years ago Yep, could do! Although, just to keep in mind:
- to update services, use
docker service update - to remove services, use
docker service rm - to deploy new service, use
docker stack deploy - updating a service who hasn't changed does not trigger any action and would normally not cause any problems
If this creates unwanted update, it's because we're not yet pinning container versions where we should, separate issue
In testnet, we use 02apps.yml for all app (tomoscan, tomomaster, faucet, netstats, proxy)
I suggest we should separate them, e.g: tomoscan -> tomoscan.yml tomomater -> tomomaster.yml proxy, netstats, ... -> others.yml
So when we update the stacks (docker stack deploy ..), they are independent, do not effect others. Today, I tried to move tomoscan_redis to new server, I had to update/restart all services (tomomaster, tomoscan ..)