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) »
  • General Discussion (please no support requests here!) (Moderator: Michał Mach) »
  • Multiple developers / rolling out partial updates - Your thoughts? (D7)
Pages: [1]

Author Topic: Multiple developers / rolling out partial updates - Your thoughts? (D7)  (Read 1023 times)

CraveCode

  • I’m new here
  • *
  • Posts: 2
  • Karma: 0
  • CiviCRM version: 4.0
  • CMS version: Drupal 7
  • MySQL version: 5.5
  • PHP version: 5.3
Multiple developers / rolling out partial updates - Your thoughts? (D7)
October 26, 2011, 07:32:23 am
How are people distributing their drupal+civicrm project updates across multiple developers or publishing updates to existing installations?

Currently I'm using a git repository that also stores a database dump. This is working okay at the moment however we're going to need to post updates after an initial release. Obviously loading up a recent dev db dump won't work for that.

I'm concerned with how much configuration is saved in the database, making versioning very difficult. I've looked into the "Features" module, that sounded promising however there isn't any documentation on CiviCrm support.

I have to be missing something. This must be a huge topic. I'm very interested to hear what others are doing in this scenario. Thanks!

Setup:
Drupal 7
CiviCrm 4.0
Mysql 5.5
Php 5.3
Apache2
Ubuntu 10.0.4 LTS
« Last Edit: October 26, 2011, 07:59:56 am by CraveCode »

Erik Hommel

  • Forum Godess / God
  • I live on this forum
  • *****
  • Posts: 1773
  • Karma: 59
    • EE-atWork
  • CiviCRM version: all sorts
  • CMS version: Drupal
  • MySQL version: Ubuntu's latest LTS version
  • PHP version: Ubuntu's latest LTS version
Re: Multiple developers / rolling out partial updates - Your thoughts? (D7)
October 27, 2011, 02:57:35 am
Lots of set up is stored in the database, so I can see this being an issue. In my case I am the only developer working on the project, which I suspect happens fairly often....so I use a Git repo too. Interested to read other experiences!
Consultant/project manager at EEatWork and CiviCooP (http://www.civicoop.org/)

CraveCode

  • I’m new here
  • *
  • Posts: 2
  • Karma: 0
  • CiviCRM version: 4.0
  • CMS version: Drupal 7
  • MySQL version: 5.5
  • PHP version: 5.3
Re: Multiple developers / rolling out partial updates - Your thoughts? (D7)
October 27, 2011, 06:08:23 am
@Erik, Thanks!

Have you run into the scenario where you have to post modifications to an existing production installation? That's another big concern of mine.

Erik Hommel

  • Forum Godess / God
  • I live on this forum
  • *****
  • Posts: 1773
  • Karma: 59
    • EE-atWork
  • CiviCRM version: all sorts
  • CMS version: Drupal
  • MySQL version: Ubuntu's latest LTS version
  • PHP version: Ubuntu's latest LTS version
Re: Multiple developers / rolling out partial updates - Your thoughts? (D7)
October 27, 2011, 09:13:27 am
Yes, and in most cases it is a hook or a template customization linked to a new activity type or case type. And in that case I use the UI to make the change to the setup as it is fairly minimal.
Consultant/project manager at EEatWork and CiviCooP (http://www.civicoop.org/)
Pages: [1]
  • CiviCRM Community Forums (archive) »
  • Old sections (read-only, deprecated) »
  • General Discussion (please no support requests here!) (Moderator: Michał Mach) »
  • Multiple developers / rolling out partial updates - Your thoughts? (D7)

This forum was archived on 2017-11-26.