Please bring back QSC subcommands: dns and apache -- and maybe subcommands: database and code, too
When reading #1979224: Handbook pages out-of-date, I realized the qsc sub commands were removed (at least from command line): code, database, apache, dns, install
My team and I use this ability a lot, for similar reasons. I know in a couple cases some of these options are part of drush core. (such as create a databse or using an makefile with an install profile). and if you use SQL-LITE and don't use drush internal webserver you can spin up an instance of Drupal without need of dns & apache. However, the last two kind of circumvent part of the reason I use this environment, as I'd like to to more closely match a deployment environment.
So, here's some details on a use case:
Team environment. Useful when joining an existing project (with others on same team) where someone else has already setup the drupal environment, and possibly deployed it to a shared server.
New Client. Similar needs arise when taking on a new client and inheriting an existing drupal site.
In either case, it was easy to do something like:
drush qc dns apache database --domain=client.dev
which was useful to setup the initial environment. Then in some fashion we'd copy (usually a drush group.alias, to rsync and sql-sync) from staging/production to local to bring in the codebase and import a db.
Comments
Comment #1
traviscarden commentedThis makes total sense. I regret that the decision to remove the subcommands (options) was made in such a vacuum. Let's put these back in and then see if we can get some feedback from the community on functional needs for commands in general.
Comment #2
mike stewart commentedhmm. perhaps a knee jerk reaction. it might make more sense to utilize other existing drush commands for similar features
Comment #3
mike stewart commentedha! or what you said ;-)
edit: just noticed my post removed "assigned-to" and I can't reassign to you
Comment #4
traviscarden commentedGive it back. ;-)
Comment #5
c13l0 commented@mikestewart, thanks very much for the accurate description of how/why these commands are needed and used! Thanks Traviscarden for listening =) Looking forward to the new updates *subscribing*
Comment #6
traviscarden commentedA quick update: My professional and private lives have been such of late that I'm not able to devote any time to this at the moment. If someone wants to supply a patch, I'd gladly commit it. I apologize that I can't just do it myself right now.
Comment #7
traviscarden commentedOops. I fixed this ages ago and forgot to update the issue. See e5541eb.