A new feature for SilverStripe should be ...

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

2 votes
Vote
Sign in
Check!
(thinking…)
Reset
or sign in with
  • facebook
  • google
    Password icon
    I agree to the terms of service
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    Klemen N shared this idea  ·   ·  Admin →

    2 comments

    Sign in
    Check!
    (thinking…)
    Reset
    or sign in with
    • facebook
    • google
      Password icon
      I agree to the terms of service
      Signed in as (Sign out)
      Submitting...
      • 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.

      Feedback and Knowledge Base