-
Notifications
You must be signed in to change notification settings - Fork 51
Archive this project? #105
Comments
Add
to your favorite bash/zsh configuration. It will do as long as your
|
We have some environments where we strip our git information after deployment, so @chx functions won't work. However, we were able to have some results with the following:
|
I built off of @gagathos solution and made it replace our existing Drush commands 👍 🥇
Place the file somewhere in your path (for us it was /usr/local/bin/drush to replace drush-global-launcher). The drush command at the end of the script will pass the variables sent to the script to drush. Voila! We can finally write this off internally now.
We had so many issues trying to keep this just as a function. We had so many cases where this was failing that we just put the file back in place of the original and made it do what we assumed was the same thing. Edit: For the time being we're going back to Drush 11 and Drush Global Launcher. |
I decided that bash-based solution wasn't good enough so I went and learned Go. I needed a plan for Drush 12. 🚀 |
IMO this project has lived its useful life and should be archived. In its place we promote the alternatives listed in the README.
This project is not up to date with Drush 12 and its not clear how to make it so.
webflo/drupal-finder
to find a Drupal site. Drush no longer uses that, in favor of Composer Runtime API. drupal-finder requires adding paths to composer.json.extra to locate DrupalRoot - Drush doesn't need that. This discrepancy will likely cause issues in both launcher and drush projects.vendor/bin/drush
and instead calls drush_main() directly. So Drush has to guess these paths for Launcher users.I'm inclined to throw an Exception in drush_main() in Drush 12 to indicate that Launcher is incompatible.
The text was updated successfully, but these errors were encountered: