|
71 | 71 | # - /etc/drush/sites |
72 | 72 | # @endcode |
73 | 73 | # |
74 | | -# If you run the command `drush core:init`, this configuration will |
75 | | -# be done for you automatically. |
| 74 | +# It is also possible to create a named location that contains a group |
| 75 | +# of related site aliases. For example, if you had a number of sites |
| 76 | +# for local schools, you could define a location named "schools": |
| 77 | +# |
| 78 | +# @code |
| 79 | +# drush: |
| 80 | +# paths: |
| 81 | +# alias-path: |
| 82 | +# - '${env.home}/.drush/sites/schools' |
| 83 | +# @endcode |
| 84 | +# |
| 85 | +# Site aliases stored in this directory may then be referenced by its |
| 86 | +# full alias name, including its location, e.g.: |
| 87 | +# |
| 88 | +# $ drush @schools.example.dev |
| 89 | +# |
| 90 | +# Such alias files may still be referenced by their shorter name, e.g. |
| 91 | +# `@example.dev`. Note that it is necessary to individually list every |
| 92 | +# location where site alias files may be stored; Drush never does recursive |
| 93 | +# (deep) directory searches for alias files. |
| 94 | +# |
| 95 | +# The command `drush core:init` will automatically configure your |
| 96 | +# ~/.drush/drush.yml configuration file to add `~/.drush/sites` and |
| 97 | +# `/etc/drush/sites` as locations where alias files may be placed. |
76 | 98 | # |
77 | 99 | # Files stored in one of the search path locations can be used to create |
78 | 100 | # aliases to local and remote Drupal installations. These aliases can be |
|
85 | 107 | # |
86 | 108 | # $ drush site:alias @self |
87 | 109 | # |
| 110 | +# The `site:alias` command may also be used to list all of the sites and |
| 111 | +# environments in a given location, e.g.: |
| 112 | +# |
| 113 | +# $ drush site:alias @schools |
| 114 | +# |
| 115 | +# Or it may be used to list all of the environments in a given site: |
| 116 | +# |
| 117 | +# $ drush site:alias @example |
| 118 | +# |
| 119 | +# If called without any parameters, it will list all of the sites and |
| 120 | +# environments in all locations. |
| 121 | +# |
88 | 122 | # Drush also supports *remote* site aliases. When a site alias is |
89 | 123 | # defined for a remote site, Drush will use the ssh command to run |
90 | 124 | # the requested command on the remote machine. The simplest remote |
|
0 commit comments