CiviCRM Community Forums (archive)

*

News:

Have a question about CiviCRM?
Get it answered quickly at the new
CiviCRM Stack Exchange Q+A site
This forum was archived on 25 November 2017. Learn more.
How to get involved.
What to do if you think you've found a bug.



  • CiviCRM Community Forums (archive) »
  • Old sections (read-only, deprecated) »
  • Support »
  • Using CiviCRM »
  • Post-installation Setup and Configuration (Moderator: Dave Greenberg) »
  • Best practises for configuration and change management
Pages: [1]

Author Topic: Best practises for configuration and change management  (Read 604 times)

Tom

  • Guest
Best practises for configuration and change management
July 06, 2010, 11:31:25 pm
At present we are deep into an evaluation of CiviCRM and to date are liking what we see.  One particular issue which we would appreciate advice on is best practises in CiviCRM for configuration and change management.  As an organisation we have a strong development and testing process and would like to explore the best method of applying incremental configuration changes developed and tested in staging environments to a production server.

For instance; say we have already rolled out CiviCRM to one of our areas of work and after several months of use in the wild tweaks are required to various forms and custom fields.  These changes are made and QA'd within our test environment, what is the best method to take a snapshot of these changes and apply them to our production site?

Kurund Jalmi

  • Administrator
  • I’m (like) Lobo ;)
  • *****
  • Posts: 4169
  • Karma: 128
    • CiviCRM
  • CiviCRM version: 4.x, future
  • CMS version: Drupal 7, Joomla 3.x
  • MySQL version: 5.5.x
  • PHP version: 5.4.x
Re: Best practises for configuration and change management
July 07, 2010, 12:14:27 am
1. Read http://en.flossmanuals.net/CiviCRM/
2. Do not modify core code.
3. If any customization needed use hooks and custom templates.
4. Check on forums if you have any issues.
5. CiviCRM has quick release cycle, so if possible you should always upgrade to latest stable. Note that with each release comes lots of fixes, few features and also few bugs :)

HTh
Kurund
Found this reply helpful? Support CiviCRM

Tom

  • Guest
Re: Best practises for configuration and change management
July 07, 2010, 02:25:15 am
Our change management question is revolves around how we manage settings which are created through the web rather than filesystem based objects (templates, hooks etc).  For instance is it possible to dump custom fields from one instance and load them into another?

Donald Lobo

  • Administrator
  • I’m (like) Lobo ;)
  • *****
  • Posts: 15963
  • Karma: 470
    • CiviCRM site
  • CiviCRM version: 4.2+
  • CMS version: Drupal 7, Joomla 2.5+
  • MySQL version: 5.5.x
  • PHP version: 5.4.x
Re: Best practises for configuration and change management
July 07, 2010, 02:40:09 am

we have a set of scripts in:

bin/migrate/*.php

which help you move all custom fields / profiles (and a few other objects) from one instance to the other. Would be great if the community can help and make those tools more robust. I think there are a few drupal modules that might serve as good examples that we could learn from

lobo
A new CiviCRM Q&A resource needs YOUR help to get started. Visit our StackExchange proposed site, sign up and vote on 5 questions
Pages: [1]
  • CiviCRM Community Forums (archive) »
  • Old sections (read-only, deprecated) »
  • Support »
  • Using CiviCRM »
  • Post-installation Setup and Configuration (Moderator: Dave Greenberg) »
  • Best practises for configuration and change management

This forum was archived on 2017-11-26.