We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Since Drush 9, we can use environment variables in aliases definitions, which is a great feature to centralize datas in .env file.
In short, ${env.PROJECT_SSH_USER} is replaced by PROJECT_SSH_USER environment value, as described in https://www.drush.org/latest/site-aliases/#environment-variables
${env.PROJECT_SSH_USER}
PROJECT_SSH_USER
There are other related features (eg. env-vars), but I think this interpolation could be a nice addition to wp-cli aliases in a first place.
The text was updated successfully, but these errors were encountered:
Sounds great! Would love to see a pull request for this. We can follow Drush's implementation.
Sorry, something went wrong.
Related wp-cli/wp-cli#5566
No branches or pull requests
Since Drush 9, we can use environment variables in aliases definitions, which is a great feature to centralize datas in .env file.
In short,
${env.PROJECT_SSH_USER}
is replaced byPROJECT_SSH_USER
environment value, as described in https://www.drush.org/latest/site-aliases/#environment-variablesThere are other related features (eg. env-vars), but I think this interpolation could be a nice addition to wp-cli aliases in a first place.
The text was updated successfully, but these errors were encountered: