Posted by davidburns on February 19, 2008 at 10:30pm
I'm excited to begin working with this module. It has been quite the task to enable a module or change a permissions setting across 40 sites, having to log into each one or via update.php.
So my question is, how would this integrate into a collection of 30 - 40 established sites in a multisite configuration?
Is this something that needs to be implemented from stage 1?
I read the description of what the HM2 does but am still a little unclear how it handles modules.
Can I enable/disable modules via HM2?
Can I modify access controls across all domains and/or each domain via HM2?
Thanks,
Dave
Comments
Some pointers
HM2 has an import function to suck in existing sites.
HM2 is meant to work with install profiles. You assign an install profile to a site that is managed. So, you could add a module to an install profile, and that module would become available to all sites assigned to that install profile. You could write an update hook to enable it automatically for you.
There are limited "dashboard" modules that function across all sites. HM2 is built so that you can write your own custom provisioning and mass operations. This can be done to include a GUI and access through the web interface or you can use only the provisioning back end, which works with drush so that you can script any aspect of your mass install.
So the short answer is, you'll need to write a dashboard module to enable you to manage access controls across all domains.