7

Motivation: we're looking into building something in this space for a current project, so this question is intended to identify what approaches are already available / being utilised.

For multi-developer and multi-branch workflows, it would be beneficial to "wrap up" site configuration and have it able to be merged into the site before deployment.

I see that there are some approaches to this already:

For comparison, in host-CMS space there are different approaches also:

My question here is: how are people managing and deploying configuration in CiviCRM today?

2

CiviCRM Features looked like it had promise: https://www.drupal.org/project/features_civicrm

I spoke to the former maintainer, Tim Mallezie, about this a while ago. He was very helpful. The module was proving hard to maintain, as each entity in CiviCRM required it's own handler (perhaps this is something CiviCRM Entity could help with); and the overhead was proving too much to be worth continuing development.

At the time Tim noted that:

...we now use the CiviCRM API in custom modules with update hooks to deploy CiviCRM configuration.

1

When I posted this question in 2015, we were looking at implementing something. The result, which is not a complete solution as of March 2017, was this extension.

Ultimately, we ended up doing something else on that project, which was exporting specific CiviCRM tables and copying them across from dev ➡ stage ➡ prod.

I've documented what did and didn't work over on the extension README, and happy to discuss further. Posting this to follow up and as a pointer for future searchers.

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

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