Skip navigation

Provision CiviCRM


Provision CiviCRM

provision_civicrm helps manage the CiviCRM configurations (installation, upgrade) for Drupal sites managed with Aegir.


  • drush_make. Version >= 2.3 is required if you want to download l10n files.

    • c.f. #1134326: Allow a DrushMakeProject to be installed in a non empty directory.
  • provision. Version >= 1.3 is required if you have multi-lingual CiviCRM (which requires triggers/views).

    • See: #881496: Problem migrating sites with mysql views
    • and #1274896: migrate fails if l10n or logging is enabled.


Download the provision_civicrm module, either:

drush dl provision_civicrm-6.x


git clone git://

You should install it in ~/.drush/provision_civicrm. The git master branch is usually stable.

Creating a CiviCRM platform

provision_civicrm assumes that if you have a CiviCRM installation in your sites/all/modules/civicrm, then this is a CiviCRM platform and CiviCRM should be installed automatically.

(A cleaner way, in theory, would be to have an install profile and let the user configure it through the front-end, patches welcome! -- however, you do not want any site to simply enable CiviCRM from the Drupal admin/build/modules, so having dedicated platforms for CiviCRM makes sense in any case.)

A sample drush makefile is provided with provision_civicrm.

Assuming you are running as the user 'aegir', whose $HOME is /var/aegir/, save this in a file such as ~/makefiles/drupal-6.22-civicrm-3.3.4.make

Then create the new platform:

mkdir ~/platforms/drupal-6.22-civicrm-3.3.4
cd ~/platforms/drupal-6.22-civicrm-3.3.4
drush make ~/makefiles/drupal-6.22-civicrm-3.3.4.make

You can now add your platform in the Aegir front-end and then create new sites.

Need help?


The notebook section provides a way for you to store and share information with your group members. With the book feature you can:

  • Add book pages and organize them hierarchically into different books.
  • Attach files to pages to share them with others.
  • Track changes that others have made and revert changes as necessary.
  • Archive books that are no longer of interest to the group. Archived books can be reactivated later if needed.