-
Notifications
You must be signed in to change notification settings - Fork 27
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
Support non-composer D7 installs #35
Comments
@DuaelFr Could you post your composer.json as well? |
Sure!
(I told you it is not a project built with composer ^^) |
|
It works, thanks! |
How did you make it work? I got the same issue on my D7 non-composer install :D |
Here is my composer.json file. My drupal root is located in the
I suppose the only important line is the |
Ok there you are. This is my working composer.json for D7 installations.
|
Sorry to bother, but could you please point me to where I could learn how to use this composer.json to enable drush for my non-composer created vagrant D7 site? Where do I put his file, and what do I then to to run it and enable drush? |
@wdseelig – Seems off-topic to me, as this is the drupal-finder repo, not drush-launcher. But for what it's worth: It's absolutely not recommended (not supported) to use a local Drush in a non-Composer managed site. See drush-ops/drush-launcher#33 (read until the end). You are putting your site at risk doing it that way. Since running Instead consider to Composerize your project using https://github.com/grasmash/composerize-drupal first. |
@wdseelig what's saying @leymannx have a lot of sense. I did this for a custom need so please keep this in mind. In my example I just added a |
Hiya, |
While in a D7 root directory, I can't use drush launcher because it does not recognize a Drupal installation.
My D7 is not installed via composer (5 years old project).
It is in a www folder, at the same level of the composer.json that's used to require drush 8.
The text was updated successfully, but these errors were encountered: