Search code examples
civicrm

Deploy configuration of CiviCRM components between staging and production


There are multiple instances of a Drupal/CiviCRM installation, one at localhost, at the developers' computer, one staging site and one production site. The production site is already in use. How can I move changes between different instances? For example a new contribution page or a priceset or a membership setting? In Drupal, there is features. What is the best practise for CiviCRM?


Solution

  • There's no handy thing like the Features module to export configuration changes in CiviCRM. You can write an extension that configures everything using the API. However, that's usually overkill for something like you describe.