Configuration Management

The challenge:
You have a big Tiki project and you want to use the traditional development, staging, and production setup.

How do you deal with the code, design, content and configuration?

Wishes

• A way to easily check on which server I am (which doesn't get overwritten with rsync)
• Quick way to compare the configurations between the three sites
• Make it possible to identify a site as staging or development and have different settings, such as
  • <META NAME="ROBOTS" CONTENT="NOINDEX, NOFOLLOW">

Dev, Test, Prod

• Dev: 9.x
• Test: 8.x latest
• Prod: 8.x older

Before doing svn up on prod, we do svn up on test, and we do a diff of:

• svn diff test
• svn diff prod

Related links

• Pre-Dogfood Server
• Continuous Integration
• http://en.wikipedia.org/wiki/Development_environment_(software_development_process)
• The Drupal community is working on this:
  • http://groups.drupal.org/node/155559
  • http://london2011.drupal.org/sites/default/files/Content_Staging_and_Deployments_in_Drupal_0.pdf