Drupal Answers is a question and answer site for Drupal developers and administrators. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I've put my Drupal installation in Git so that it is easier to replicate the production site on my development system. Then I discovered drush and I think it's way cool. But then it occurred to me: If I use drush on my development box to update a module, then the source code changes will be in git and will end up in production by way of git.

But what about the database changes? How do I apply those in production? Is it sufficient to run drush updatedb in production (after using git to transfer the code)?

I'm not sure the version numbers are relevant for this question. Anyhow, running Drupal 6 currently, planning to upgrade to Drupal 7.

share|improve this question
up vote 2 down vote accepted
  1. Yes, if you update the files on the production site, all you have to do is to run the update.php or drush updatedb additionally.

  2. For migrating functionality from staging to production site, you might be interested in Features. It allows you to export various "pieces" of functionality and transfer them to another installation; this can include content types, fields, views and image styles, to name a few.

Hope this helps!

share|improve this answer
Instead of features you could use Configuration Manager – ropic May 20 at 5:01

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.