CiviCRM Community Forums (archive)

With bigger projects we tend to put all configuration stuff into a generic config extension?

This is during development, once the environment is live each change is dealt with individually.

You develop an extension where contact sub types, activity types, groups, custom groups etc. are generated (based on json files). Whenever a configuration item on the development sandbox is promoted, it is added to the json files. In the target environment(s) you initially install the extension and then install changes with a clearcache?

Perhaps I'm being pedantic, but how do you deal with changes in a live site?

@Erik Hommel: I like the idea of having a json file that installs or updates different configuration objects. Is there any where I could see an example of that? 

@JohnFF: I've considered that approach too, but I'd really prefer not to be shuffling DB's back and forth. It also really only allows for a single branch of development, which is part of the issue I'm trying to handle.