I'm currently working on a website using Drupal 8, with 3 other members in my team.

We use git as a versioning system, and we very often work at the same time on different branches.

Here is the problem :

  • If we all use local databases, then it's a mess when we have to merge our code, because we have to isolate the parts of the database that have changed, and create a patch, or re-create the changes ourselves a second time. For example if I have created many static pages, I have to create them again, or export the part of the database containing them.
  • If we choose to share a database to avoid that problem, then every time someone runs the drush cr command, everyone's website gets synched to their last changes, erasing every other changes from other teammate, which can be very confusing and annoying.

What is the right solution here?

  • Are you familiar with these docs: drupal.org/documentation/administer/config and drupal.org/node/1667894 ? Commented Mar 31, 2015 at 0:33
  • @DavidThomas I wasn't familiar with it. Although I'm not sure it will solve my problem. If I work with several people at the same time, we have several dev environment, everyone can export their own configuration and import it on the live environment, but we will still step on each other's toes, won't we? I'll export my configuration, then my coworker will export his, and it will erase mine... Commented Mar 31, 2015 at 0:41

1 Answer 1


Checkout configuration management in Drupal 8. Though there are many modules that can help you out but most of them are in active development and not stable for production use yet.

Two most promising modules are Configuration Update module and Features module.

Checkout What are the alternatives to Features module in Drupal 8 for further notes.

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

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