-
-
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
site-install fails when site alias doesn't have defined root #4059
Comments
Sort of random note, but I found that in BLT's case (which passes site URI via drush config file), the VALUE of the |
Pull requests welcome - I probably won't have time to get to this for a while. |
I'd love to help @greg-1-anderson but I now get a "talking to" at my employer for contributing code to the community. ¯_(ツ)_/¯ 🤦♂ |
We also want this as we have aliases without root. EDIT: We want to ssh to aliases without root. |
Trivial PR flying in: consolidation/site-alias#37 I can now do EDIT: Said PR has a wrong approach. |
As clarified in the abandoned PR, the ssh use case has a different fix that this. So opened #4211. |
On site-install: TBH, i do not see where drush should install when no root is given. |
Presumably at the cwd. |
Describe the bug
When running
drush si
with an alias that has no root defined in Drush 9.6.2, you get an exception as described below. This seems to be related to a change in consolidation/site-alias, although I'm not clear on the full history: acquia/blt#3204To Reproduce
Start from a vanilla Drupal codebase. Create a file
drush/sites/foo.site.yml
:Now run
drush @foo.local si
.(You don't actually need to set up sites.php or anything, since the site-install fails long before that.)
Expected behavior
Site to install.
Actual behavior
Workaround
Define a root in the alias file (which is specific to the local machine and not useful across teams). Use the workarounds described in acquia/blt#3204 (comment)
System Configuration
Additional information
Using site aliases without a defined root is useful when you want to share local multisite aliases across teams for the purposes of installing a particular site (i.e. mostly just defining a uri).
The text was updated successfully, but these errors were encountered: