From ac8c3fffc85c272f7a2efe7bc8232334d36b724d Mon Sep 17 00:00:00 2001 From: Mitchell Hashimoto Date: Thu, 9 Jul 2015 10:39:33 -0600 Subject: [PATCH] website/docs: doc options for NFS [GH-5583] --- .../docs/source/v2/synced-folders/nfs.html.md | 18 ++++++++++++++++++ 1 file changed, 18 insertions(+) diff --git a/website/docs/source/v2/synced-folders/nfs.html.md b/website/docs/source/v2/synced-folders/nfs.html.md index 0e9d87e50..8aedf6188 100644 --- a/website/docs/source/v2/synced-folders/nfs.html.md +++ b/website/docs/source/v2/synced-folders/nfs.html.md @@ -65,6 +65,24 @@ the final part of the `config.vm.synced_folder` definition, along with the * `nfs_version` (string | integer) - The NFS protocol version to use when mounting the folder on the guest. This defaults to 3. +## NFS Global Options + +There are also more global NFS options you can set with `config.nfs` in +the Vagrantfile. These are documented below: + +* `functional` (bool) - Defaults to true. If false, then NFS won't be used + as a synced folder type. If a synced folder specifically requests NFS, + it will error. + +* `map_uid` and `map_gid` (int) - The UID/GID, respectively, to map all + read/write requests too. This will not affect the owner/group within the + guest machine itself, but any writes will behave as if they were written + as this UID/GID on the host. This defaults to the current user running + Vagrant. + +* `verify_installed` (bool) - Defaults to true. If this is false, then + Vagrant will skip checking if NFS is installed. + ## Specifying NFS Arguments In addition to the options specified above, it is possible for Vagrant to