Why is the documentation for v2 up when I can only get the latest 1.7.3?

48 views
Skip to first unread message

Tim Dockins

unread,
Jul 16, 2015, 6:40:20 PM7/16/15
to vagra...@googlegroups.com
This is somewhat misleading!  I was looking for documentation on shared_folders.  V2 has changed this to synced_folders!


Seth Vargo

unread,
Jul 16, 2015, 6:43:01 PM7/16/15
to vagra...@googlegroups.com
Hi Tim,

The v2 documentation does correspond to the latest release. Is there a particular page you are referring to? We can definitely get that fixed up. "v2" refers to the version of the documentation, not Vagrant itself.

Best,
Seth

On Jul 16, 2015, at 3:40 PM, Tim Dockins <timdo...@gmail.com> wrote:

This is somewhat misleading!  I was looking for documentation on shared_folders.  V2 has changed this to synced_folders!



--
This mailing list is governed under the HashiCorp Community Guidelines - https://www.hashicorp.com/community-guidelines.html. Behavior in violation of those guidelines may result in your removal from this mailing list.
 
GitHub Issues: https://github.com/mitchellh/vagrant/issues
IRC: #vagrant on Freenode
---
You received this message because you are subscribed to the Google Groups "Vagrant" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vagrant-up+...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/vagrant-up/858e7949-de16-40d6-87d6-122035423960%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

dragon788

unread,
Aug 3, 2015, 1:34:40 PM8/3/15
to Vagrant
Tim, to add to what Seth mentioned, the documentation is actually referring to the Vagrant API version. Early Vagrant versions used a 1.0 or lower version, after around Vagrant 1.2 or so they revamped the entire API but maintained most of the backwards compatibility, but the API version is a flag now inside the Vagrantfile. You are correct that synced_folders did change, but unless you were coming from a pre-1.0 Vagrant or hadn't used 'vagrant init' with a recent version of Vagrant, you should have been using V2 all along.
Reply all
Reply to author
Forward
0 new messages