Author Topic: drush civi question (Read 845 times)

Eileen · May 13, 2010, 04:39:03 am

I tried posting this on Drupal IRC but no response yet & I am turning into a pumpkin so I think I'd better post it here instead. (not implying that I waited a long time for a response & didn't get one - just that I need sleep)

My civi drush install command fails because it can't find the civicrm codebase. The codebase is in sites/all/modules but it is looking in sites/sitename/modules

The variable that is in question is $siteRoot:
$siteRoot = drush_get_context('DRUSH_DRUPAL_SITE_ROOT', FALSE);
$modPath = "$drupalRoot/$siteRoot/modules";

So, I guess the question is where does DRUSH_DRUPAL_SITE_ROOT come from?

torenware · May 25, 2010, 09:15:20 pm

Eileen,

I don't know if this is a standard way to do this, but here's what I find works for me.

Using Drush v.3, I call drush via wrapper scripts that look like this:

Code: [Select]

#! /bin/bash
#export XDEBUG_CONFIG="remote_port=9000 remote_enable=1"
DRUP_INSTALL=/home/production/sites/demdata_v2/phase1
DRUSH_INSTALL=/home/production/sites/demdata_v2
exec $DRUSH_INSTALL/drush/drush.php -l  https://migrate -r $DRUP_INSTALL $@

DRUP_INSTALL points to my drupal install directory (i.e., where index.php lives). Drush itself is not in the Drupal tree, but is at DRUSH_INSTALL/drush/. Note also the -l argument to the drush.php command, which you need to worry about if you use apache name-based hosting and Drupal's own multisite capabilities, as I do. Getting -l right makes sure that Drush uses the correct settings.php and civicrm.settings.php files.

Note also I have commented out XDEBUG_CONFIG, which if you use an xdebug based source code debugger, can be very handy. I can actually debug stuff from the command line by uncommenting this, which is bloody handy.

CiviCRM Community Forums (archive)

News:

Author Topic: drush civi question (Read 845 times)

Eileen

drush civi question

torenware

Re: drush civi question