-
-
Notifications
You must be signed in to change notification settings - Fork 17
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
lando drupal
broken due to upstream issue/breaking changes
#11
Comments
Alright I've got another workaround for the meantime, assuming you've already ran
Actually, another option would be to include |
This started giving me a permissions error that I couldn't sort out, so added a tooling override instead:
|
Add it as a custom tool, by adding the following line to
then restart lando with |
@yuseferi yup, that's what my last comment says to do :) |
What if |
@CheckeredFlag this solution requires that your drupal project itself composer requires drupal/console. I don't think I've hit dependency hell requiring console, so I unfortunately cannot speak to that, but without installing via composer the bin/drupal script and it's reqs won't exist anywhere. |
Updated an older |
is there a work around. I am having issues with drupal console using lando's drupal 9 recipe. I tried install and build gloablly and but I get the following:
and when I go with the composer route I am having dependency issues and even when I resolve them I get a lot of missing console commands which I presume it's a drupal console issue. |
Per hechoendrupal/drupal-console#4262, there appears to be an issue with the installer (https://drupalconsole.com/installer) being unavailable. This is causing
lando drupal
to throw/usr/local/bin/drupal: 2: /usr/local/bin/drupal: Syntax error: redirection unexpected
since the 500 page contents are being downloaded instead of the installer itself.In that issue, the maintainer noted that
As such, it might be a good idea to figure out how to remove the dependency on the installer itself. Somebody in the ticket noted that a dirty workaround is to grab a copy of the
drupal
executable from elsewhere (an env that still/already has it) and use that directly. So, something like adding that executable to a known url and grabbing it from there instead.In either case,
lando drupal
is broken until the installer issue is handled.The text was updated successfully, but these errors were encountered: