drush

Posted by: 
Dominique De Cooman

The goal of automating deployment is to make introducing new features easier. In this post we will learn how to set up a workflow that will move code and configuration of your drupal site from your local development station, to development, to staging and to production all by a using your version control and a push of a button.

Posted by: 
Dominique De Cooman

To speed up indexing of our nodes and making full use of our machine, we want to index our nodes concurrent.

Drupal launch batch with drush

This shows how to process batch jobs with drush.
Executing batch jobs that have already been set and the use of stub functions for executing batch jobs with scripts.

http://drupal.org/node/873132

Posted by: 
Dominique De Cooman

As discussed in previous blog post, drush cron can be run from crontab too. While seeming pretty straightforward, trying it out caused some troubles.

The thing you would do to make drush run from crontab is:

$ crontab -e
* * * * * drush -r /path/to/drupal

Also tried to give full path to drush install

$ crontab -e

Posted by: 
Dominique De Cooman

Sometimes there is a need to make drupal redirect using drupal_goto. We had to do it in an SSO scenario. We had to make drupal goto a configurable admin page (node page) when no roles where assigned to you by the external authentication (shibboleth). So we would put a check in hook_init() to redirect drupal when our criteria where met.

Posted by: 
Dominique De Cooman

By big imports I mean creating millions of nodes and indexing them fo apache solr search. We needed to import 1 million records from file, 3 nodes for each record, one in each of our 3 languages. These nodes also had 3 taxonomy vocabularies, around 30 cck fields and we also needed to join another table containing a spatial coordinates for our geo field.

Subscribe to drush