Submitted by Darren on Tue, 09/12/2008 - 11:41
A major pain point for developers is migrating configuration from development versions of sites, to production environments. It's difficult in Drupal because configuration is in the database, and made more difficult when using CCK because content and configuration are so tightly coupled.
One approach to solving this is using a module to store your configuration and using "upgrade" hooks to deploy configuration changes and do any required content migration. A fellow Drupal developer Tim Millwood started a discussion on this and I threw in my two pence worth this morning.
Post new comment