Here is a scenario:
You have 100 nearly identical sites running under drupal multisite.
You want to have an ability to install/remove modules centrally, from one place and want this change to take effect over all (or specified) sites.
Currently, this is somewhat possible with shared table in multisite, since you share module data for all sites in the same place. But you have to enable each module manually on each sites admin page.
So, ideally, on module administration page you would have a checkboxes next to each module that would say: install this module for all sites. Also, all module settings would apply to all sites.
In the case of all prefixed tables, I think it is possible to write some script that will be applying module installation/removal/settings data to all prefixed tables. Resource consuming - yes, hard to do - hopefully not. Also, this way enables tweaking module settings for each site separately, if you wish to do so.
Delf.
Comments
Comment #1
schuyler1d commentedYeah, the actual install across sites shouldn't be too hard. This is a great idea, on where to take the module.
Ruminating where this feature leads to:
* install modules
* uninstall modules
* configure modules (could be hard)
Hmm. Maybe a button on the bottom of the module-installer page along with 'Save' OR 'Update Multisites'. Alternatively, we can put an extra check-box next to each module in the installer form to correspond to multisite-installation.
And for each config screen, there's another button?
Even further down the line, do an action based on category that the multisite is in?
Are you interested in developing this (or helping), or is this a feature request only? :-)
Comment #2
tatien commentedI am interested in developing this. I'll start doing it today.
Comment #3
schuyler1d commentedI haven't checked it out, yet, but this module:
http://drupal.org/project/rollout
looks like it might be what we're looking for. Perhaps all that's necessary is making sure the two modules are compatible--and maybe integrating the two together in any important way.
Comment #4
tatien commentedAll right, I'll have a look at it. I have started working on the patch and ... well... it isn't obvious at all. The rollout module seem to have found a clean solution to this, I'll check it out.
Comment #5
schuyler1d commentedTook a look at rollout, myself. The client-server API seems like a good way to go, but will need some heavy security.
It's fantastic that you're working on this. If you settle on an approach before a full patch, please post it here.