# Discourse Docker Manager: Upgrade All

**URL:** <https://meta.discourse.org/t/discourse-docker-manager-upgrade-all/33808>\
**Category:** Feature\
**Created:** [27 Septiembre, 2015 20:16 UTC](https://meta.discourse.org/t/discourse-docker-manager-upgrade-all/33808 "2015-09-27T20:16:56Z")\
**Posts on this page:** 1\
**Showing post:** 15

<div class="post-metadata">

**Author:** ![riking](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/riking/32/170938_2.png) [@riking](https://meta.discourse.org/u/riking)\
**Post date:** [23 Septiembre, 2017 05:15 UTC](https://meta.discourse.org/t/discourse-docker-manager-upgrade-all/33808/15 "2017-09-23T05:15:43Z")

</div>

I wrote the server code for executing multiple upgrades at once, but I’m having design troubles with the client code.

Branch compare: [Comparing discourse:a6539a6cf...riking:multi-upgrade · discourse/docker\_manager · GitHub](https://github.com/discourse/docker_manager/compare/a6539a6cf...riking:multi-upgrade)

The client code I’m having trouble visualizing how to refactor. I suppose a MultiRepo object constructed by the Upgrade All handler that combines together the paths/versions and presents the same interface as a Repo object? It feels like that is going to run into duck-typing problems.

---

_[View the full topic](https://meta.discourse.org/t/discourse-docker-manager-upgrade-all/33808)._