-
-
Notifications
You must be signed in to change notification settings - Fork 1.1k
Simplified site aliases. Fixes #3107 #3184
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
Conversation
|
Isolation tests are failing because a list needs to be sorted before the assertion. |
| * record. | ||
| * | ||
| * Sites may also define a special alias file self.site.yml, which | ||
| * may be stored in the drush/site-aliases directory relative to either |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks like this dir is now 'sites', not 'site-aliases'.
85bfbd5 to
446c1dc
Compare
… Require site aliases be stored in the 'sites' directory in each search location. No longer search directly in __ROOT__/drush et. al. Update 'drush init' to match (writes ~/drush/sites rather than ~/drush as the default home directory search location for site aliases).
2b755b9 to
28efe40
Compare
|
I increased the search depth of site aliases to Currently, the behavior of the site:alias command is as follows:
In the last example, environments defined in the file The next question is, should there be some way to run Or perhaps some other notation? |
5cf5ca7 to
ca44f0b
Compare
…liases to be grouped together in directories.
ca44f0b to
5eee5e3
Compare
|
All green! We could merge here and solve ^^ as a follow-on issue, or fix it up prior to merging as desired. |
|
I don't feel the need to see aliases in a particular directory. Thats
getting real close to `more /path/to/site.yml`. So, lets merge this now.
|
First pass. Mostly done.