-
-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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
Document that global Drush 8 can detect Drush 12 in a local Drupal 10 installation #5741
Comments
Confirming this works as described. Would be great to see it documented. It seems to depends on Drush 12 being available at |
Thanks for confirming @fenstrat. And yes, About paths and discoverability, I usually install Drush 8 (for Drupal 7) in Check if path
Create the folders, source them and check:
Install Drush 8.4.12 as ordinary user:
|
I am no sure if it is related, but I just got a permission error on another server, from inside the Drupal 10 installation:
I also got this:
I had to run this for it to work: After that UPDATE: It was unrelated. I found Errno 13: Permission Denied and ran these commands:
Now, permissions in The real problem was that I was running the commands in Securing file permissions and ownership not from the relocated web root ( |
I do appreciate the desire to inform. This issue lives on for anyone who needs it. However a global install of drush really isn't supported or encouraged. |
But global Drush is the recommended method of installing Drush 8 ...
If this is not the recommended method to install Drush 8 for a non-Composer Drupal 7 installation, should we instead place a separate |
The user is trying to use Drupal 10 and Drush 12 in the scenario described. A global Drush is not needed nor supported in this scenario. Call vendor/bin/drush directly. The Alternatives section may also be helpful - https://github.com/drush-ops/drush-launcher#alternatives-now-that-this-project-is-archived. |
Thanks, but the scenario is having both a Drupal7/Drush8 (non-Composer) as well as a Drupal10/Drush12 (Composer) running on the same server:
Drupal10/Drush12 is locally installed as recommended, the global installation I am referring to is Drupal7/Drush8. So my question is, if a global installation for Drush 8 is also not recommended for this set up? If not, what is the recommended method of installing Drush 8 for Drupal 7, non-Composer based? |
@greg-1-anderson is the drush8 person, but AFAIK the global drush8 is your only option for a non-composer d7 site. The fact that the same Drush can call into a Drush12 elsewhere on the system is lucky, and unsupported. |
Thanks for clearing that up @weitzman. I very much appreciate you and @greg-1-anderson's work with maintaining Drush. And sure, let's not document it, but let it stay here, for other people to find. Though, having Drupal10/Drush12 locally installed combined with global Drupal7/Drush8 scenario is not rare, so there is a risk that "something" unforeseen might happen in the future, unless it is taken into account for code updates between now and January 2025, when Drush 8 is EOL ... |
Find the path to the correct drush by an anchor positioned exactly at the base of the drupal instance Useful when your need drush for Drupal 10.2 and older
|
UPDATE: I tried removing the global Drush and it's still slow, so please disregard :) ========== Recently, it seems like the Global Drush 8 is called, even when using Scenario:
|
Existing document
https://github.com/drush-ops/drush-launcher was recently archived. On the project page, it says:
What are you attempting to do
I have both a non-Composer Drupal 7 installations with a globally installed Drush 8, and a Composer-run Drupal 10 with local Drush 12 concurrently on the same server. These two Drush versions actually seem to work well together, even without Drush Launcher, as discovered by @gisle in which drush for Drupal 10.1.2 on debian 10. Drush 8 will detect that Drush 12 is available in a Drupal 10 installation. This is great news, and should be documented.
In what way is the existing documentation unclear or incomplete
Currently, it looks like you might need to replace drush-launcher with some advanced configuration, if you want to run Drush 8 and Drush 12 on the same server, but this doesn't seem necessary.
What should the documentation say instead?
We could update the introduction, by adding a sentence that the above set up is possible, and works without any extra efforts. Suggestion:
This is just a rough draft, but let's try to figure out a good wording, and document this great feature.
The text was updated successfully, but these errors were encountered: