site provisioning/multisite management/database migration tools
At Drupalcon, there was all kind of talk around challenges like how to manage a collection of multisite installs, how to do things like run cron or update.php on 60 gazillion sites, how to enable/disable "packages" of modules/functionality to avoid having to click through 10,000 things, how to migrate database changes from one site to another, etc. I'm planning on spending a few hours this week trying out various Drupal packaging/site provisioning systems and writing up a report comparing/contrasting them. Here are the modules I know about in this space: http://drupal.org/project/patterns: Module/system configurations that can be run at any time http://drupal.org/project/hostmaster: Bryght's multisite hosting managed site deployment framework, which includes http://drupal.org/project/hosting and http://drupal.org/project/provision http://drupal.org/project/autopilot: Migrate changes from dev to live http://drupal.org/project/deploy: Migrate changes from dev to live http://drupal.org/project/drush: Command-line tool containing a bunch of useful commands such as running cron, downloading modules, etc. Any others I should be taking a look at? -Angie
I would throw Domain Access in a similar category. http://drupal.org/project/domain: "The Domain Access project is a group of lightweight modules that provide tools for running a group of affiliated sites from one Drupal installation and a single shared database." Cheers, blake hall On Mar 24, 2008, at 12:30 PM, Angela Byron wrote:
At Drupalcon, there was all kind of talk around challenges like how to manage a collection of multisite installs, how to do things like run cron or update.php on 60 gazillion sites, how to enable/disable "packages" of modules/functionality to avoid having to click through 10,000 things, how to migrate database changes from one site to another, etc.
I'm planning on spending a few hours this week trying out various Drupal packaging/site provisioning systems and writing up a report comparing/contrasting them.
Here are the modules I know about in this space:
http://drupal.org/project/patterns: Module/system configurations that can be run at any time
http://drupal.org/project/hostmaster: Bryght's multisite hosting managed site deployment framework, which includes http://drupal.org/project/hosting and http://drupal.org/project/provision
http://drupal.org/project/autopilot: Migrate changes from dev to live
http://drupal.org/project/deploy: Migrate changes from dev to live
http://drupal.org/project/drush: Command-line tool containing a bunch of useful commands such as running cron, downloading modules, etc.
Any others I should be taking a look at?
-Angie
On 24 Mar 2008, at 7:30 PM, Angela Byron wrote:
http://drupal.org/project/hostmaster: Bryght's multisite hosting managed site deployment framework, which includes http://drupal.org/project/hosting and http://drupal.org/project/provision
I just updated lots of documentation regarding this : http://groups.drupal.org/hm2/overview http://groups.drupal.org/hm2/design-terminology http://groups.drupal.org/hm2/project-goals And hostmaster uses drush to do it's job.
I and others started to pull together some notes on mass hosting needs and existing solutions here: http://groups.drupal.org/node/7196
On Mar 24, 2008, at 10:30 AM, Angela Byron wrote:
Any others I should be taking a look at?
Possibly, DAST <http://drupal.org/project/dast>. It can use custom build files to do all kinds of things on the filesystem and DB. It supports lots of Drupal friendly stuff including modules installation and install profiles as well. It could certainly be configured to handle many multisite possibilities. -Mikey P __________________ Michael Prasuhn mike@mikeyp.net http://mikeyp.net 949.200.7595 714.356.0168 cell 949.200.7670 fax
thats a really broad set of use cases. different tools will excel at each. i'd say that hostmaster and drush are very promising for most of these tasks. for moving content around, it seems that 'deploy' is most promising. as an all purpose tool, see capistrano: http://jystewart.net/process/2007/02/using-capistrano-for-drupal-deployment/. ruby is only required on the source PC, not on all the target servers. On Mon, Mar 24, 2008 at 1:30 PM, Angela Byron <drupal-devel@webchick.net> wrote:
At Drupalcon, there was all kind of talk around challenges like how to manage a collection of multisite installs, how to do things like run cron or update.php on 60 gazillion sites, how to enable/disable "packages" of modules/functionality to avoid having to click through 10,000 things, how to migrate database changes from one site to another, etc.
I'm planning on spending a few hours this week trying out various Drupal packaging/site provisioning systems and writing up a report comparing/contrasting them.
Here are the modules I know about in this space:
http://drupal.org/project/patterns: Module/system configurations that can be run at any time
http://drupal.org/project/hostmaster: Bryght's multisite hosting managed site deployment framework, which includes http://drupal.org/project/hosting and http://drupal.org/project/provision
http://drupal.org/project/autopilot: Migrate changes from dev to live
http://drupal.org/project/deploy: Migrate changes from dev to live
http://drupal.org/project/drush: Command-line tool containing a bunch of useful commands such as running cron, downloading modules, etc.
Any others I should be taking a look at?
-Angie
On 24 Mar 2008, at 9:21 PM, Moshe Weitzman wrote:
for moving content around, it seems that 'deploy' is most promising.
Personally, from all the different approaches i've tried, I think that codifying site configuration (views / cck types / variables etc) is the cleanest way to build something like this. Basically the same way that views provides it's default views. It's also the most work for module developers to set up initially. But once that's done, these things could be easily exported to a module that is very simple to keep version controlled etc, and all that's needed to change the settings/etc is to update the source and delete the caches. For instance, I have a patch for D5 (not updated to D6 yet) that allows you to specify a global $defaults array, which is used by the variable_get instead of the programmatically defined default, if nothing has been set. This way, you just have a module you enable / update that has all your site settings in it, and no additional magic is required on the developer's part.
I'm on iPhone without access to copy from one email to another, but note that walter at dharmatech.org has developed some awesome sed scripts for working with drupal and associated modules. I'll try to dig up URL, along with his contact info when I get home several hours from now. I am particularly interested in these topics, and look forward to your report. Best, Margie Sent from my iPhone On Mar 24, 2008, at 3:21 PM, "Moshe Weitzman" <weitzman@tejasa.com> wrote:
thats a really broad set of use cases. different tools will excel at each. i'd say that hostmaster and drush are very promising for most of these tasks. for moving content around, it seems that 'deploy' is most promising. as an all purpose tool, see capistrano: http://jystewart.net/process/2007/02/using-capistrano-for-drupal-deployment/ . ruby is only required on the source PC, not on all the target servers.
On Mon, Mar 24, 2008 at 1:30 PM, Angela Byron <drupal-devel@webchick.net
wrote: At Drupalcon, there was all kind of talk around challenges like how to manage a collection of multisite installs, how to do things like run cron or update.php on 60 gazillion sites, how to enable/disable "packages" of modules/functionality to avoid having to click through 10,000 things, how to migrate database changes from one site to another, etc.
I'm planning on spending a few hours this week trying out various Drupal packaging/site provisioning systems and writing up a report comparing/contrasting them.
Here are the modules I know about in this space:
http://drupal.org/project/patterns: Module/system configurations that can be run at any time
http://drupal.org/project/hostmaster: Bryght's multisite hosting managed site deployment framework, which includes http://drupal.org/project/hosting and http://drupal.org/project/provision
http://drupal.org/project/autopilot: Migrate changes from dev to live
http://drupal.org/project/deploy: Migrate changes from dev to live
http://drupal.org/project/drush: Command-line tool containing a bunch of useful commands such as running cron, downloading modules, etc.
Any others I should be taking a look at?
-Angie
Angie, Moshe, at. al. Here are the "awesome" sed scripts that I mentioned earlier, created by Walter Haas from dharmatech.org Best Regards, Margie http://justice.dharmatech.org/websvn/listing.php?repname=adm&path=%2F&sc=0 On Mon, Mar 24, 2008 at 5:36 PM, Mroswell <mroswell@gmail.com> wrote:
I'm on iPhone without access to copy from one email to another, but note that Walter at dharmatech.org has developed some awesome sed scripts for working with drupal and associated modules. I'll try to dig up URL, along with his contact info when I get home several hours from now.
I am particularly interested in these topics, and look forward to your report.
Best, Margie
Sent from my iPhone
On Mar 24, 2008, at 3:21 PM, "Moshe Weitzman" <weitzman@tejasa.com> wrote:
thats a really broad set of use cases. different tools will excel at each. i'd say that hostmaster and drush are very promising for most of these tasks. for moving content around, it seems that 'deploy' is most promising. as an all purpose tool, see capistrano:
http://jystewart.net/process/2007/02/using-capistrano-for-drupal-deployment/
. ruby is only required on the source PC, not on all the target servers.
On Mon, Mar 24, 2008 at 1:30 PM, Angela Byron <drupal-devel@webchick.net
wrote: At Drupalcon, there was all kind of talk around challenges like how to manage a collection of multisite installs, how to do things like run cron or update.php on 60 gazillion sites, how to enable/disable "packages" of modules/functionality to avoid having to click through 10,000 things, how to migrate database changes from one site to another, etc.
I'm planning on spending a few hours this week trying out various Drupal packaging/site provisioning systems and writing up a report comparing/contrasting them.
Here are the modules I know about in this space:
http://drupal.org/project/patterns: Module/system configurations that can be run at any time
http://drupal.org/project/hostmaster: Bryght's multisite hosting managed site deployment framework, which includes http://drupal.org/project/hosting and http://drupal.org/project/provision
http://drupal.org/project/autopilot: Migrate changes from dev to live
http://drupal.org/project/deploy: Migrate changes from dev to live
http://drupal.org/project/drush: Command-line tool containing a bunch of useful commands such as running cron, downloading modules, etc.
Any others I should be taking a look at?
-Angie
Here are two approaches that migrate changes from dev to live (and to other developers' instances). They both involve some low-level database stuff, which may make them not suitable for the average Drupal user. I'm no expert in the projects you listed, but I think these two address some things the others do not. http://drupal.org/node/181128 http://www.dave-cohen.com/node/1779 There was some discussion about this sort of thing at DrupalCon Boston. No clear best practices came from that BOF: http://boston2008.drupalcon.org/session/updating-and-upgrading-live-sites http://www.mikiane.com/node/2008/03/04/live-blogging-drupalcon-boston-2008 -Dave On Monday 24 March 2008, Angela Byron wrote:
At Drupalcon, there was all kind of talk around challenges like how to manage a collection of multisite installs, how to do things like run cron or update.php on 60 gazillion sites, how to enable/disable "packages" of modules/functionality to avoid having to click through 10,000 things, how to migrate database changes from one site to another, etc.
I'm planning on spending a few hours this week trying out various Drupal packaging/site provisioning systems and writing up a report comparing/contrasting them.
Here are the modules I know about in this space:
http://drupal.org/project/patterns: Module/system configurations that can be run at any time
http://drupal.org/project/hostmaster: Bryght's multisite hosting managed site deployment framework, which includes http://drupal.org/project/hosting and http://drupal.org/project/provision
http://drupal.org/project/autopilot: Migrate changes from dev to live
http://drupal.org/project/deploy: Migrate changes from dev to live
http://drupal.org/project/drush: Command-line tool containing a bunch of useful commands such as running cron, downloading modules, etc.
Any others I should be taking a look at?
-Angie
This sounds very similar to a GHOP task, which could serve as a starting point: http://drupal.org/node/197950 --Larry Garfield On Mon, 24 Mar 2008 13:30:17 -0400, Angela Byron <drupal-devel@webchick.net> wrote:
At Drupalcon, there was all kind of talk around challenges like how to manage a collection of multisite installs, how to do things like run cron or update.php on 60 gazillion sites, how to enable/disable "packages" of modules/functionality to avoid having to click through 10,000 things, how to migrate database changes from one site to another, etc.
I'm planning on spending a few hours this week trying out various Drupal packaging/site provisioning systems and writing up a report comparing/contrasting them.
Here are the modules I know about in this space:
http://drupal.org/project/patterns: Module/system configurations that can be run at any time
http://drupal.org/project/hostmaster: Bryght's multisite hosting managed site deployment framework, which includes http://drupal.org/project/hosting and http://drupal.org/project/provision
http://drupal.org/project/autopilot: Migrate changes from dev to live
http://drupal.org/project/deploy: Migrate changes from dev to live
http://drupal.org/project/drush: Command-line tool containing a bunch of useful commands such as running cron, downloading modules, etc.
Any others I should be taking a look at?
-Angie
You could use http://drupal.org/project/drush_mm for enabling/disabling modules. It is not meant to be a D7 ever and not tested for D6) (I wrote this module because enabling ubercart was a drag.) Thanks for your effort! On Mon, 2008-03-24 at 13:30 -0400, Angela Byron wrote:
At Drupalcon, there was all kind of talk around challenges like how to manage a collection of multisite installs, how to do things like run
-- Clemens Tolboom http://build2be.com
On Mon, Mar 24, 2008 at 2:30 PM, Angela Byron <drupal-devel@webchick.net> wrote:
I'm planning on spending a few hours this week trying out various Drupal packaging/site provisioning systems and writing up a report comparing/contrasting them.
http://drupal.org/project/hostmaster: Bryght's multisite hosting managed site deployment framework, which includes http://drupal.org/project/hosting and http://drupal.org/project/provision
Probably a stupid question, but since there is no code placed here, how does one go about testing them (I've wanted to for some time)? I would appreciate being pointed in the right direction to obtaining this code for trying it out. Thanks, Victor Kane http://awebfactory.com.ar
The code for provision is http://cvs.drupal.org/viewvc.py/drupal/contributions/modules/provision/ but it would be nice to have a DEV version available. You could file an issue. On Tue, 2008-03-25 at 06:32 -0300, Victor Kane wrote:
Probably a stupid question, but since there is no code placed here, how does one go about testing them (I've wanted to for some time)?
I would appreciate being pointed in the right direction to obtaining this code for trying it out.
Thanks,
Victor Kane http://awebfactory.com.ar -- Clemens Tolboom http://build2be.com
On 25 Mar 2008, at 11:44 AM, Clemens Tolboom wrote:
The code for provision is http://cvs.drupal.org/viewvc.py/drupal/contributions/modules/ provision/ but it would be nice to have a DEV version available. You could file an issue. That was on purpose. i didn't want the great unwashed masses installing it yet, and i've been making considerable effort to make sure that each commit to head (recently) is of -dev release quality anyway.
I'm getting close to making a release though, once I hit feature parity for what I want for the initial release. (still in the process of documenting my roadmap, will be on g.d.o soon)
participants (12)
-
Adrian Rossouw -
Angela Byron -
Blake Hall -
Clemens Tolboom -
Dave Cohen -
Larry Garfield -
Marjorie Roswell -
Michael Prasuhn -
Moshe Weitzman -
Mroswell
-
Nedjo Rogers -
Victor Kane