Re: site provisioning/multisite management/database migration tools

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/0
2/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-develwebchick.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://d
rupal.org/project/hostmaster: Bryght's multisite hosting
managed
>  site deployment framework, which includes
>  http://drupal.org/p
roject/hosting and http://drupal.org
/project/provision
>
>  http://d
rupal.org/project/deploy: Migrate changes from dev to
live
>
>  

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"
<weitzmantejasa.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-develwebchick.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://d
rupal.org/project/hostmaster: Bryght's multisite hosting
 
>> managed
>> site deployment framework, which includes
>> http://drupal.org/p
roject/hosting and http://drupal.org
/project/provision
>>
>> http://d
rupal.org/project/deploy: Migrate changes from dev to
live
>>
>>