Drush 2.0 released - Screencast 1: Installing Drush and getting started

After a long period of development the Drush team (myself, and the multi-talented rockstars Moshe Weitzman and Adrian Rossouw) have finally released Drush 2.0.

This is a milestone in many ways - the core of Drush has been completely rewritten (some parts of it twice over!) since the last stable release. This core can now (among other things) connect to multiple major Drupal versions, work reliably (we hope!) on a wide range of command line environments - but is also a powerful platform that allows commands to specify dependencies, to work at different levels of the Drupal bootstrap, call other commands (including on remote servers over secure SSH connections) and provide responses in both machine readable formats and nicely laid out human readable formats. There are also many improvements in the set of commands that come with Drush, both adding new functionality as well as making the existing functionality more intuitive to use.

Over the next few days, I will be uploading a series of short screencasts, covering how to get started, going through the various commands in some detail, and perhaps getting into some detail about how to write your own commands.

Here is the first in the series. Please add any questions in the comments, and I will try and address them (either in the next video, or in the issue queue).

Comments

Comment viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.

syncsvnc

Thanks for drush - an excellent tool! Does drush still support the --syncsvn (or was it --svnsync) option that I found so useful?

Indeed - that option still

Indeed - that option still works --version-control=svn --svnsync

Thanks Owen

for the work on Drush and for the screencast. Looking forward to more.

Remote website administration via drush

As I see - drush for now usable only with local drupal installation But very usefull as for me - remote admin using drush.

remote admin using drush

well, drush has some tools for running remote commands using the --backend flag. feel free to peruse backend.inc. this code is used primarily by aegir project. check it out.

Good Start

Looks super cool. I really like the idea of pulling Drush out of the modules directory. But Drush 2 running on windows is even less stable that Drush 1 was. I opened a couple of issues in the queue. I am not sure if the best approach is to try to get it working in cmd.exe (like I did for Drush 1), or to try to get it working inside a CygWin bash shell (which is made trickier with the current incompatibility with the version of tar that ships with CygWin).

Yeah - none of the

Yeah - none of the maintainers works on Windows on a daily basis - while we try and stay "theoretically" compatible there are always issue that crop up. We welcome patches, however :) I would guess that Cygwin would be a happier environment for drush (assuming I can't persuade you to switch to Ubuntu ;)). The tar issue looks like it should be pretty easy to tweak the drush wget package handler to handle the odd version issue. You could also work around by using the CVS package handler.

Drush works very well over an

Drush works very well over an SSH connection, if that is what you mean. For programmatic remote access the --backend parameter feeds back usefully structured information (as JSON) on the results of your action. Remote access to sites that are accessible only over FTP/sftp is another kettle of fish, however - and is something we haven't looked at at all.

Andriy Podanenko, You can

Andriy Podanenko, You can install and run drush on a remote server. We are doing this at CivicActions. Though I'm not sure if that was actually your question or not...

This looks great. Would be

This looks great. Would be using it myself if I was able to gain SSH access to where my site is hosted. Will give it a try locally though.