-
-
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
Alias documentation for Drush 9 beta7 seems to be incorrect #3097
Comments
If Drush is not searching site-aliases for aliases, that is a bug. At the moment, Drush never searches into subfolders for aliases -- they must either exist directly in the search location, or directly in the search location + A file called We are not going to remove the |
The instruction
sounds like one alias in such a file. No? |
One site, multiple environments. |
Maybe the point is that we should rename from ALIASNAME.alias.yml to SITENAME.site.yml. |
~/.drush/site-aliases works for me as a valid location to store site alias files. |
I was also able to successfully use:
However, the later only works if
|
We're going to remove the group alias feature altogether, which means that the |
Wanted to follow the instructions in
examples/example.aliases.yml
but the instructions don't seem to be accurate. Here are some issues I found:Stuff in those subdirectories (site-aliases) are not recognized, they have to be in the drush directory itself to be recognized.
The first one only works, when the file itself contains an alias name again which results in an alias @aliasname.aliasname instead of just @Aliasname.
The second and the third option require the root element
sites:
which seems redundant and I suggest to remove that.The text was updated successfully, but these errors were encountered: