Skip to content

Conversation

@weitzman
Copy link
Member

Remove the finder and launcher. The recommended way to run Drush is to call vendor/bin/drush from the root of your project or anywhere inside the docroot. This new flexibility comes from the DrupalFinder, which is now called from within drush_locate_root().

This PR also adds a sut script at the root of our project. That lets you run drush commands on your SUT for drush development purposes.

There may be more to clean up in backend and sitealiases related to this PR. Input welcome.

The drush-shim is our early attempt at a global launcher. Lets discuss that at https://github.com/webflo/drush-shim/issues

$options['alias-path'] = array('context' => 'ALIAS_PATH', 'local-context-only' => TRUE, 'merge-pathlist' => TRUE, 'propagate-cli-value' => TRUE, 'description' => "Specifies the list of paths where drush will search for alias files.", 'example-value' => '/path/alias1:/path/alias2');
$options['confirm-rollback'] = array('description' => 'Wait for confirmation before doing a rollback when something goes wrong.');
$options['complete-debug'] = array('hidden' => TRUE, 'description' => "Turn on debug mode forf completion code");
$options['php-options'] = array('description' => "Options to pass to `php` when running drush. Only effective when using the drush.launcher script.", 'never-propagate' => TRUE, 'example-value' => '-d error_reporting="E_ALL"');
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

What happened to php-options? Don't we still need this in backend invoke?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants