## Problem Statement Users running multi tenancy setups with a large number of servers, running on docker.<br> From what I've investigated docker compose does not give crafty enough time to close all servers before killing the container, so for multi tenancy setups with lots of servers a lot of them will just get killed outright without saving chunks. <br> If there is a stop all button a server admin can set a job to iterate through all servers stopping them safely, where they can then stop the container. ## Who will benefit? Docker users running compose, possibly docker run too ## Benefits and risks What benefits does this bring? - reduced support issues regarding docker users - attempt to one of the supported platforms - prevent end user server world corruption What risks might this introduce? - users need to manually do this before they stop their container - formatting on mobile will need to be accounted for - documentation for docker users would need updated ## Proposed solution A small button at the top of the dashboard detailed `Stop All` even `start/restart` all. ## Priority/Severity - [ ] High (This will bring a huge increase in performance/productivity/usability) - [x] Medium (This will bring a good increase in performance/productivity/usability) - [ ] Low (anything else e.g., trivial, minor improvements)