haskal
/
vagrant
1
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity

[docs] add example for 'env' option

This commit is contained in:
nqb 2019-12-11 16:09:07 +01:00
parent f306131a97
commit 10018641a5
No known key found for this signature in database
GPG Key ID: E5DC9201AE579262
1 changed files with 11 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

11
website/source/docs/provisioning/shell.html.md
View File

@ -52,6 +52,17 @@ The remainder of the available options are optional:
the script. Vagrant will handle quoting for environment variable values, but the script. Vagrant will handle quoting for environment variable values, but
the keys remain untouched. the keys remain untouched.
Example:
```ruby
s.env = {
PERL_TESTS: "ENV['PERL_TESTS'] || yes",
GOLANG_TESTS: "ENV['GOLANG_TESTS'] || yes"
}
```
This syntax allow you to redefine environment variables on command line when
running Vagrant: `PERL_TESTS=no vagrant up`.
* `keep_color` (boolean) - Vagrant automatically colors output in green and * `keep_color` (boolean) - Vagrant automatically colors output in green and
red depending on whether the output is from stdout or stderr. If this is red depending on whether the output is from stdout or stderr. If this is
true, Vagrant will not do this, allowing the native colors from the script true, Vagrant will not do this, allowing the native colors from the script