# \`docker\_manager\` should go first
**URL:** https://meta.discourse.org/t/docker-manager-should-go-first/187085
**Category:** Feature
**Created:** [April 16, 2021, 11:30am UTC](https://meta.discourse.org/t/docker-manager-should-go-first/187085 "2021-04-16T11:30:10Z")
**Posts on this page:** 9
**Page:** 1
### Author:  [@hellekin](https://meta.discourse.org/u/hellekin)
#### Post date: [April 16, 2021, 11:30am UTC](https://meta.discourse.org/t/docker-manager-should-go-first/187085/1 "2021-04-16T11:30:10Z")
On the upgrade page, it’s always a drag having to wait for all plugins to check for new updates, and end up with `docker_manager` needing to be upgraded first. Is there a way to make this happen, that before checking for any new version, the upgrade system first checks whether `docker_manager` needs to be updated? It would save a lot of HTTP requests and some time for admins who tend to spend more time than necessary performing upgrades.
---
### Author:  [@david](https://meta.discourse.org/u/david)
#### Post date: [April 16, 2021, 11:57am UTC](https://meta.discourse.org/t/docker-manager-should-go-first/187085/2 "2021-04-16T11:57:28Z")
Sounds like a good idea to me, I’m sure it would be #pr-welcome if someone would like to work on it 🙂
---
### Author:  [@Jim\_Starkweather](https://meta.discourse.org/u/Jim_Starkweather)
#### Post date: [April 16, 2021, 2:51pm UTC](https://meta.discourse.org/t/docker-manager-should-go-first/187085/3 "2021-04-16T14:51:03Z")
An excellent idea. Always having to scroll down to check it first.
---
### Author:  [@david](https://meta.discourse.org/u/david)
#### Post date: [April 16, 2021, 3:08pm UTC](https://meta.discourse.org/t/docker-manager-should-go-first/187085/4 "2021-04-16T15:08:18Z")
I decided to give this a try. PR here: [UX: Always show the docker\_manager plugin second in the list by davidtaylorhq · Pull Request #100 · discourse/docker\_manager · GitHub](https://github.com/discourse/docker_manager/pull/100)
That will always put docker\_manager second in the list, after `discourse` itself:
Edit: That’s merged 🎉
---
### Author:  [@hellekin](https://meta.discourse.org/u/hellekin)
#### Post date: [April 16, 2021, 4:42pm UTC](https://meta.discourse.org/t/docker-manager-should-go-first/187085/5 "2021-04-16T16:42:54Z")
Thank you @david! Does it skip the checks for other plugins if `docker_manager` is not up-to-date?
---
### Author:  [@david](https://meta.discourse.org/u/david)
#### Post date: [April 16, 2021, 4:47pm UTC](https://meta.discourse.org/t/docker-manager-should-go-first/187085/6 "2021-04-16T16:47:35Z")
No it doesn’t skip them, but it means the docker\_manager one happens first. An admin can then click the docker\_manager update button immediately, even while the other plugins are loading.
I think it’s still useful to see whether other plugins have updates available, even if you can’t install them immediately?
---
### Author:  [@hellekin](https://meta.discourse.org/u/hellekin)
#### Post date: [April 16, 2021, 6:43pm UTC](https://meta.discourse.org/t/docker-manager-should-go-first/187085/7 "2021-04-16T18:43:07Z")
Usually when you see a new `docker_manager` release it’s because a new Discourse release was announced in your admin notifications, so you would most probably do 1. upgrade `docker_manager`, then 2. upgrade all, 80 to 90% of the time.
When you want to check for a single plugin you scroll down anyway. I’m simply thinking about wasted resources. After some years of upgrades, across thousands of instances, that would make a lot of saved resources.
I suppose a middle ground would be to kill the check requests when the `docker_manager` upgrade button is clicked. But I would expect that simply _not_ checking when this plugin is out-of-date would be the most sensible – I do not have stats, maybe you do.
---
### Author:  [@david](https://meta.discourse.org/u/david)
#### Post date: [April 16, 2021, 7:11pm UTC](https://meta.discourse.org/t/docker-manager-should-go-first/187085/8 "2021-04-16T19:11:54Z")
> [@hellekin](#):
>
> I do not have stats, maybe you do.
We don’t use docker\_manager on our managed hosting, so no stats I’m afraid.
But ‘checking for updates’ is a super cheap thing to do. Under the covers, `docker_manager` is doing a `git remote update` on every plugin. It only pulls across the changes since the last check, so the data transfer should be tiny.
---
### Author:  [@david](https://meta.discourse.org/u/david)
#### Post date: [April 23, 2021, 7:00am UTC](https://meta.discourse.org/t/docker-manager-should-go-first/187085/9 "2021-04-23T07:00:43Z")
This topic was automatically closed after 6 days. New replies are no longer allowed.