Hostmaster 2 requirements on Drush

These are notes posted by Adrian, following some initial code development based in part on Drush.

The requirements I had for Drush were

1) required parameter handling. In the form of
./drush.php provision $urlhere

This is already implemented it turns out, so that when you define a command
called 'provision', any extra parameters are automatically passed to the callback.

2) multiple Drupal systems through a central drush.php

This also already exists, via a -path argument. More on this later.

3) Force loading of modules.

I decided this would be best done by implementing a .drushrc config file, which will
allow you to set any of the config settings. Most specifically, the include path, in the
standard form of 'path:/path:/path2' , and some code to manipulate module_list.

This will allow us to store the drush / provision code outside of the drupal tree entirely,
and stop us from needing to have a hide_modules module.

4) install mode bootstrap.

Since I use a copied chunk of code from install.php, I think I might be able to modify it to
install sites by switching into another database using db_set_active. This would simplify
the code we need to write in Drush, but it's also significantly different from what we have in
hostmaster at the moment.

This will require more research.