Recent blog posts
- Six Tips For Writing Better Web Content
- Overview of Google authentication methods
- Drupalcon SF Session Proposal: Guerilla Usability Testing
- Drupalcon SFO Session Proposal & demo: Developing Apps for iPhone/iPad/Android using drupal as Base System
- DrupalCon SF session proposal: Coder Module: Easily Port Modules to Drupal 7
- CivicActions Team DrupalCon San Francisco 2010 Sessions - Vote Now
- [BSP] Blatant (DrupalCon) Session Promotion: Open Source Opens Doors for Youth
- WYSIWYG Tips And Tricks
- Upgrading CiviCRM from 2.x to 3.x Tips And Tricks
- More Drupal Training Opportunities And A Look Back



















Comments
Setting options with drushrc.php
I found creating drushrc.php from example.drushrc.php and setting a few options helpful. Running updates as user 1 is sometimes essential.
// always run as user 1$options['u'] = 1;
// set package handler to CVS$options['package-handler'] = 'cvs';
package-handler=cvs
is there any benefit to use cvs as the handler instead of the normal built in wget? the only thing i can think of is if it it cvs it might keep any changes i make to the files (assuming the newer version doesnt modify that text). other than that using the normal method you can still use the updatecode or update commands to update the modules. Also how does the cvs method handle if i have installed a patch to one of the files after updating the cvs modules
This screencast Tutorials are
This screencast Tutorials are really useful which dives deep into the drush. I really thank for the author for posting quality info.
Thankyou Owen thankyou
thankyou Owen