Testing Sanity

The core task of software development is sanity testing.

  • warning: Creating default object from empty value in /home2/thepalls/public_html/cgpsoftware/modules/taxonomy/taxonomy.pages.inc on line 34.
  • warning: Parameter 2 to gmap_gmap() expected to be a reference, value given in /home2/thepalls/public_html/cgpsoftware/includes/module.inc on line 483.
  • strict warning: Non-static method view::load() should not be called statically in /home2/thepalls/public_html/cgpsoftware/sites/all/modules/views/views.module on line 879.

best practices

Posted by cgp

Drupal deployments & workflows with version control, drush_make, and Aegir.

I'm not familiar with Aegir and this is a complicated issue, I was thinking about more granularly (is that a word) deploying modules using cvs and this technique which is a little more lightweight (and probably cheaper), but I could see where the other approach would have it's strengths.

As with any technology or process choice, there are pros and cons to each.

Clearly, again, the one take away from all of this is that drush is awesome.