Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

How is the drush directory intended to be used? #166

Closed
jhedstrom opened this issue Jun 20, 2016 · 2 comments
Closed

How is the drush directory intended to be used? #166

jhedstrom opened this issue Jun 20, 2016 · 2 comments

Comments

@jhedstrom
Copy link

This project ships with a drush directory, which includes a policy.drush.inc file intended to disallow folks from using the legace package management drush utilities in favor of composer. However, in my testing, this directory isn't used without manual intervention. If it were moved to web/drush, then it's inclusion would be automatic. If moving it isn't an option, then perhaps documentation on how to integrate this folder into drush's command discovery would be useful.

This came up in phase2/generator-gadget#66.

@jhedstrom
Copy link
Author

Interesting, so if run from within the web directory (eg, ../vendor/bin/drush), then this works as-is.

@jhedstrom
Copy link
Author

Ah, I hadn't realized that drush itself had been updated to search one directory back (../drush) in \Drupal\Boot\DrupalBoot::commandfile_searchpaths():

        $searchpath[] = $drupal_root . '/../drush';

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

No branches or pull requests

1 participant