Closed (fixed)
Project:
Quickstart: Prebuilt Drupal Development Environment
Component:
Drush
Priority:
Normal
Category:
Feature request
Assigned:
Unassigned
Reporter:
Created:
6 May 2011 at 22:17 UTC
Updated:
11 Jul 2012 at 16:26 UTC
http://drupalcontrib.org/api/drupal/contributions--drush--examples--exam...
* For example:
*
* # File: mysite.aliases.drushrc.php
* $aliases['dev'] = array(
* 'root' => '/path/to/drupal',
* 'uri' => 'dev.mydrupalsite.com',
* );
* $aliases['live'] = array(
* 'root' => '/other/path/to/drupal',
* 'uri' => 'mydrupalsite.com',
* );
Comments
Comment #1
MichaelCole commentedComment #2
mike stewart commentedIf I understand the issue, this means as part of
drush quickstart-create --domain=blah.devwill also have an option to create an alias file: ~/.drush/blah.aliases.drushrc.php -- with at least a local alias.Hmm, how would you feed the info (path/ssh user/db user/etc ...) for stage/production? Starting to think this is more of a drush feature that quickstart can utilize. Heck, does it already exist?
Comment #3
Sean Buscay commentedHi Mike.
Would the alias be useful locally? Such as the site created us blah.dev and the alias created is @blah_dev. Then drush cc all @blah_dev would clear the cache for the site blah.dev, no matter what directory drush was run from.
I could see this as useful, though I just habitually switch to the directory of the site I'm working in. However it could be useful to say run drush commands on multi local sites.
This is probably just a nice to have.
We could take a contrib / patch for it, if someone really wants it. Thoughts?
Comment #4
mike stewart commented@Sean, drush supports @self as default alias. The real qustion I have would be how to cleanly / simply create a default alias. It'd definitely be a nice to have each time you setup a site ... but most of my thoughts are in #2. To try to be more clear, I don't see a way to automate this ... I also don't like the idea of passing passwords through a shell prompt as part of a command (means password gets stored in a log, and is bad practice).
But mostly, I'm not convinced this is a quickstart feature as much as its a drush feature. (and for all I know, already exists). I'd like more input from the community. Maybe when/if we split off the quickstart drush commands as a module, then maybe makes more sense.
Comment #5
mike stewart commentedI'm removing assignment to me since I'm no longer maintaining the 7.x-2.x branch (its moved to DrupalPro Development Desktop), and I'm not sure of the future of Quickstart 2.x except that it wont be based on Ubuntu 12.04LTS (Unity)
Comment #6
MichaelCole commented