This is something Plushu could conceivably implement, probably as a new type of retrieval method (an alternative to plushu-git): something with locations and a manifest of all latest versions.
The main advantage to this would be that updating each plugin (and setup and service and buildpack etc.) could be done with 1 network request instead of 50.
This could even just work as a thin layer on top of the existing Git stuff: if a plugin is checked out to a different version than the listed latest, pull it. (And if the plugin doesn't exist in the manifest, do a git pull for it the way we do now.)
Anyway, what we have now works fine - the slowness isn't an issue, considering that updating the entire server is something you should do, like, a few times a week max (more like a few times a month or year). Taking 30 seconds, over which you can see steady progress, isn't a major disaster.
This is something Plushu could conceivably implement, probably as a new type of retrieval method (an alternative to
plushu-git): something with locations and a manifest of all latest versions.The main advantage to this would be that updating each plugin (and setup and service and buildpack etc.) could be done with 1 network request instead of 50.
This could even just work as a thin layer on top of the existing Git stuff: if a plugin is checked out to a different version than the listed latest, pull it. (And if the plugin doesn't exist in the manifest, do a git pull for it the way we do now.)
Anyway, what we have now works fine - the slowness isn't an issue, considering that updating the entire server is something you should do, like, a few times a week max (more like a few times a month or year). Taking 30 seconds, over which you can see steady progress, isn't a major disaster.