Exporting configuration to code [Solved]

[John.K]

Hi, I was wondering if there is a way of exporting CiviCRM configuration (custom fieldsets for example) to code, so that it can easily be moved between staging and live environments?

I had a quick search but couldn't find anything?

[JonGold]

There's three options available last I checked:
Hmm, scratch that.  Looks like https://www.drupal.org/project/features_civicrm has been abandoned.

One option: Use CiviConfigure to export settings (https://civicrm.org/extensions/civiconfigure).  Never used this, can't speak to it.

My preferred option: The CLI CSV API export tool (there's also a GUI version available as an extension).  Here's a blog post about it: https://civicrm.org/blogs/xavier/api_batch_tools

php /path/to/modules/civicrm/bin/csv/export.php -e CustomGroup > groups.csv
php /path/to/modules/civicrm/bin/csv/export.php -e CustomField > fields.csv

php /path/to/modules/civicrm/bin/csv/import.php -e CustomGroup --file=`pwd`/groups.csv
php /path/to/modules/civicrm/bin/csv/import.php -e CustomField --file=`pwd`/fields.csv

That would export/import ALL custom fieldsets, and doesn't cover option values.  Check the blog post for filtering just the ones you want - at which point exporting the option values should become fairly self-explanatory as well.

[John.K]

Cool, thanks for the (quick!) response Jon, good to know there are some options around.

I hadn't clicked that these were exposed to the API - it would be fairly straightforward to just use the API export/import things I expect (particularly custom field sets etc.)

[Coleman Watts]

Extensions tend to use the "managed" api to, well, manage things.
http://wiki.civicrm.org/confluence/display/CRMDOC/hook_civicrm_managed