dev-test-prod staging workflow for drupal with transport of database changes Hi I am looking for a best practice staging workflow for a four level staging environement for drupal:

dev->test->pre-prod->prod

I found this quite informative thread already Applying Updates to Multiple Drupal Sites

As the Teams will change especially on the test upwards it has to be pretty straight forward.


I guess we will move everting as far as posible through git or would rsync be better choice?
Is there some way to maintain some kind of central stage configuration where you just maintain the server adresses e.g. in on central place
How to move database changes without conflicting with productive content


Would be great if someone could share hints to some documentation of such a workflow.

Thanks in advance
Regarding #2, I would recommend using drush site aliases.  See also the sync_enable example in Drush, which demonstrates how you can get Drush to automatically adjust your database settings when you move your db from prod towards dev.  For moving configuration from dev to production, many folks use features; you might also want to look at ctools export bonus, which is built on much of the same technology.