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

website/docs: Fix example of v1 config option invalid in v2 

Fix the name of the old v1 option, `config.vm.forward_port`, used as an example of an invalid option in v2.
This commit is contained in:
Christian G. Warden 2013-11-06 19:47:50 -08:00 committed by Teemu Matilainen
parent 0041b2ba50
commit 93c739c47e
1 changed files with 1 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
website/docs/source/v2/vagrantfile/version.html.md
View File

@ -36,7 +36,7 @@ for each version, and properly merges them, just like any other configuration.
The important thing to understand as a general user of Vagrant is that The important thing to understand as a general user of Vagrant is that
_within a single configuration section_, only a single version can be used. _within a single configuration section_, only a single version can be used.
You can't use the new `config.vm.provider` configurations in a version 1 You can't use the new `config.vm.provider` configurations in a version 1
configuration section. Likewise, `config.vm.forwarded_port` won't work configuration section. Likewise, `config.vm.forward_port` won't work
in a version 2 configuration section (it was renamed). in a version 2 configuration section (it was renamed).
If you want, you can mix and match multiple configuration versions in the If you want, you can mix and match multiple configuration versions in the