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 »
  • Installing CiviCRM »
  • Drupal Installations (Moderator: Piotr Szotkowski) »
  • Best Practice: Dev to Staging / Production Workflow
Pages: [1]

Author Topic: Best Practice: Dev to Staging / Production Workflow  (Read 1038 times)

sonicthoughts

  • Ask me questions
  • ****
  • Posts: 498
  • Karma: 10
Best Practice: Dev to Staging / Production Workflow
August 03, 2012, 12:54:03 pm
I've been trying to configure a WAMP stack which runs my site nicely to push changes to a staging server (using GIT).  CiviCRM has several places that refer to filesystem and domain locations so pushing causes problems.  The target machine has a different URL so I can configure a seperate settings file, but the database also has hard locations which do not seem to be over-ridden by the settings file.  I'm wondering if anyone has a nice development workflow for making local changes and pushing them.  I've been trying out pantheon which works really nicely for drupal but has been a bare to config w/ civicrm. 

Any best practices?

sonicthoughts

  • Ask me questions
  • ****
  • Posts: 498
  • Karma: 10
Re: Best Practice: Dev to Staging / Production Workflow
August 03, 2012, 01:14:40 pm
I just found this: http://wiki.civicrm.org/confluence/display/CRMDOC41/Override+Server+Directory+and+URL+Settings which is a nice way to manage the file issues ...!
Pages: [1]
  • CiviCRM Community Forums (archive) »
  • Old sections (read-only, deprecated) »
  • Support »
  • Installing CiviCRM »
  • Drupal Installations (Moderator: Piotr Szotkowski) »
  • Best Practice: Dev to Staging / Production Workflow

This forum was archived on 2017-11-26.