Hi, I created a blog post on how I got site_update to work on our Aegir server:

http://druplicity.com/content/drupal-staging-problem-site-update

Was quite happy with the results, yet wondered what your take on CCK tables might be.

It would be great to be able to add/remove/change CCK fields in the base, which would then automatically be created on the dev/live machine. To enable such a thing, the content tables that are created when adding fields would have to be reproduced on the live & dev servers.

CommentFileSizeAuthor
#4 aegir-support-1081230-4.patch1.84 KBrobin van emden

Comments

Dave Cohen’s picture

Dave Cohen commented
Title: Site update module on Aegir » Site update support CCK

Agreed. I'm sort of a throwback in the drupal world, not a CCK user. Unheard of, I know, but that's why I haven't yet had to tackle that in this module.

It might require something similar to the treatment of modules and themes. That is, include the necessary info in the dump file, and use drupal_execute() to ensure the settings are correct.

I'd welcome any patches along these lines. As I said, I simply haven't needed it yet.

Dave Cohen’s picture

Dave Cohen commented

Also, If you bundle those aegir changes as a patch, I will get them into the next release.

robin van emden’s picture

robin van emden commented

Thanks for your fast response! I will roll a patch for site_update this weekend. I will also look into the CCK issue, shouldn't be too difficult to create something along the lines you suggest.

robin van emden’s picture

robin van emden commented
StatusFileSize
new aegir-support-1081230-4.patch1.84 KB

First Drupal.org Git patch for me, hurray! Attached patch adds basic Aegir support to site_update.

One more thing to keep in mind when using both Aegir & Site Update:

Before running an update, there is one additional step specific to multi-site installs. Site_update by default looks for the SQL file in sites/all/database. In the case of a multi-site install you have to tell every site where its particular site_update.sql resides. Normally you set this path in settings.php. Within an Aegir controlled environment, you have to add the path to a local.settings.php file (since Aegir is allowed to override settings.php).

<?php
//put the following in the sites settings.php or local.settings.php
$conf['site_update_sql_file'] = 'sites/devsite/database/site_update.sql';
Dave Cohen’s picture

Dave Cohen commented
Issue summary: View changes
Status: Active » Closed (won't fix)

Wont fix this issue against 6.x.

The 7.x branch is now quite capable of handling fields.