Module/extension management module
Module management - it would be great to have a CMS-based module management "module".
1. Minimal/basic functionality:
- List of modules & versions in CMS
- Module Actions (delete / upgrade)
- Specify "Suggested" vs "Required" modules when creating libraries
- can rely heavily on Composer.json
I'd be keen to implement this. I've had a bit of funding to investigate this but have put it on the backburner. If there is interest I'll pick it back up to finish it off
AdminIngo Schommer (Admin, SilverStripe) commented
I think now that semantic versioning is more established in the wider SilverStripe ecosystem, that becomes more feasible. I'd expect the main use case would be patch-level upgrades of existing modules for security releases. In practice, it means that you opt out of maintaining a composer.json and composer.lock as part of your website repository, and bypass other controls like UAT environments, pre-deploy builds etc. That might be feasible for some projects, but I don't think it'll serve the wider community well in terms of making this a core feature - one aspect that has always distinguished SilverStripe is the certainty of what is getting deployed: You don't have to deal with database state merges for configuration, since it's all in code (and your repo).
You might want to dig through groups.google.com/forum/#!forum/silverstripe-dev, this idea has been discussed before there.