This project is not covered by Drupal’s security advisory policy.

Drush drake is a module to enable drush based setting and configuration migrations from developers machines to external environments. If you are looking to migrate content or users, you are probably looking for the migrate module.

The goal is to allow developers to write scripts of drush commands that alter drupal setups (i.e. variables table, module enabling/disabling, permissions). These scripts are easily executed within the context of drush, and can be stored in a source control system such as git or svn. With one command you can update shared development, staging, and production environments in a serial and traceable way.

Below is an example of the steps you could take to enable and configure the apachesolr module with drush. From the command line:

bkennedy$ drush drake-file
Created scripts/drush_drake/1281650462.drake for migrating
bkennedy$ vim scripts/drush_drake/1281650462.drake
>>
#enable apachesolr module
en apachesolr
#set host to localhost
vset apachesolr_host localhost
#set port to 8080
vset apachesolr_port 8080

After saving this you now have an environment migration file setup. Simply execute it with:

bkennedy$ drush drake
Completed execution of scripts/drush_drake/1281650462.drake

To make things even easier, there is a drush_migrate module included in the package that allows system settings forms to be exported to drake files through the admin panel. This allows developers to quickly create drake migration scripts to export variables without needing to necessarily know what their names are. It also allows you to set array data through drush.

DISCLAIMER:

This module is not recommended for production use at this time. There is a lot of feature development going on right now, and some command names might end up changing. That being said, please leave feedback or feature requests in the issue queue.

Project information

  • Created by brianpkennedy on , updated
  • shield alertThis project is not covered by the security advisory policy.
    Use at your own risk! It may have publicly disclosed vulnerabilities.

Releases