vagrant-sshfs 1.2.0 → 1.2.1

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA1:
-  metadata.gz: 74c0ac801cbf4908bc4c4afa128e205764b899fd
-  data.tar.gz: 0e842c7729c4bd1a746aa41c16506006720722a9
+  metadata.gz: 5dfa628705000436923d10ab6c28c81b0a0224f0
+  data.tar.gz: dcbd353a54a12bfbc5fe3c44673b027213d7873b
 SHA512:
-  metadata.gz: a2727626ab76dab2502ba3671e36999dbfd38efbba0528089d43f2f80169c862ed4555c70b8dd2acaa57873123511a1e60537ae8255f1edc331df0cf43d21615
-  data.tar.gz: abee837f9c6b2bd264204ae6990523213d3951c6dfe2a00e063a028ec4a7cd51e370c555a78805e8008a9983c4700efc003aac36f90f5daca02c6abe40333d98
+  metadata.gz: 93ef3f2a946e095d197cd49a9af02cbbc83970905a867f1a5092a71e13c10e313392337f373396058f391830b49fa0120b2bde0e8a442d900c168a781c8cbe2e
+  data.tar.gz: 74aad85b4d51019b5af792be1feebf4e99f6c59edab6d8299f723dd12bcd1ccfd288a4b205aef733f732fbd2a224c97b52af46dcd5c09e20751673e5942956b4

data/Gemfile

@@ -6,7 +6,7 @@ group :development do
   # We depend on Vagrant for development, but we don't add it as a
   # gem dependency because we expect to be installed within the
   # Vagrant environment itself using `vagrant plugin`.
-  gem "vagrant", :git => "https://github.com/mitchellh/vagrant.git", :ref => 'v1.8.4'
+  gem "vagrant", :git => "https://github.com/mitchellh/vagrant.git", :ref => 'v1.8.6'
 end
 
 group :plugins do

data/README.adoc

@@ -0,0 +1,307 @@
+= vagrant-sshfs
+:toc:
+:toc-placement!:
+
+This Vagrant plugin adds synced folder support for mounting
+folders from the Vagrant host into the Vagrant guest via
+https://github.com/libfuse/sshfs[SSHFS]. In the default mode it does
+this by executing the `SSHFS` client software within the guest, which
+creates an SSH connection from the Vagrant guest back to the Vagrant
+host.
+
+'''
+toc::[]
+'''
+[[considerations]]
+== Considerations
+
+The benefits of this approach: 
+
+* Works on any host platform and hypervisor type
+** Windows, Linux, Mac OS X
+** Virtualbox, Libvirt, Hyper-V, VMWare
+* Seamlessly works on remote Vagrant solutions
+** Works with vagrant aws/openstack/etc.. plugins
+
+The drawbacks with this approach:
+
+* Performance is worse than an implementation like NFS
+* There must be `sftp-server` software on the Vagrant host
+
+`sftp-server` is usually provided by SSH server software so it already
+exists on Linux/Mac. On windows you only need to install
+https://cygwin.com/cgi-bin2/package-grep.cgi?grep=openssh&arch=x86_64[openssh]
+via https://cygwin.com/[cygwin] and you will get `sftp-server`.
+
+
+[[history]]
+== History
+
+The inspiration for this plugin came from
+https://github.com/fabiokr[Fabio Kreusch] and his
+https://github.com/fabiokr/vagrant-sshfs[code] for the original
+vagrant-sshfs Vagrant plugin. The goal of this plugin (as opposed to the
+old implementation) is to implement SSHFS as a synced folder plugin just
+like the other synced folder plugins (NFS/RSYNC/SMB/VirtualBox).
+
+This plugin was developed mainly by copying the code from the NFS synced
+folder plugin from the Vagrant core code and molding it to fit SSHFS.
+
+[[modes-of-operation]]
+== Modes of Operation
+
+[[sharing-vagrant-host-directory-to-vagrant-guest---98-of-users]]
+=== Sharing Vagrant Host Directory to Vagrant Guest - 98% of users
+
+This plugin uses SSHFS slave mounts (see
+https://github.com/dustymabe/vagrant-sshfs/issues/11[link]) to mount a
+directory from the Vagrant Host into the Vagrant Guest. It uses the
+`sftp-server` software that exists on the host and `sshfs` running in
+_slave mode_ within the guest to create a connection using the existing
+authentication over SSH that vagrant sets up for you.
+
+[[sharing-arbitrary-host-directory-to-vagrant-guest---1-of-users]]
+=== Sharing Arbitrary Host Directory to Vagrant Guest - 1% of users
+
+This plugin allows you to share a folder from an arbitrary host to the
+Vagrant Guest. This would allow you to do a folder mount to some other
+host that may have files that you need. To do this the plugin will run
+an SSHFS command from the Guest and connect to the arbitrary host that
+must have an SSH daemon running. You must provide the `ssh_host` option
+in the Vagrantfile to get this to work. You can use ssh key forwarding
+or username/password for authentication for this.
+
+See link:#options-specific-to-arbitrary-host-mounting[Options] and
+link:#appendix-a-using-keys-and-forwarding-ssh-agent[Appendix A] for
+more information.
+
+[[sharing-vagrant-guest-directory-to-vagrant-host---1-of-users]]
+=== Sharing Vagrant Guest Directory to Vagrant Host - 1% of users
+
+_NOTE:_ This option is dangerous as data will be destroyed upon
+`vagrant destroy`
+
+This plugin allows you to share a folder from a Vagrant guest into the
+host. If you have workloads where there are a lot of disk intensive
+operations (such as compilation) it may be ideal to have the files live
+in the guest where the disk intensive operations would occur. For
+discussion see https://github.com/dustymabe/vagrant-sshfs/issues/7[Issue
+#7].
+
+See link:#options-specific-to-reverse-mounting-guest-host-mount[Options]
+for more information on how to enable this type of mount.
+
+[[getting-started]]
+== Getting Started
+
+In order to use this synced folder implementation perform the following
+steps:
+
+[[install-plugin]]
+=== Install Plugin
+
+In order to install the plugin simply run the following command:
+
+....
+# vagrant plugin install vagrant-sshfs
+....
+
+[[add-sshfs-synced-folder-in-vagrantfile]]
+=== Add SSHFS Synced Folder in Vagrantfile
+
+Edit your Vagrantfile to specify a folder to mount from the host into
+the guest:
+
+....
+config.vm.synced_folder "/path/on/host", "/path/on/guest", type: "sshfs"
+....
+
+Now you can simply `vagrant up` and your folder should be mounted in the
+guest. For more options that you can add see the link:#options[Options]
+section.
+
+[[executing-the-vagrant-sshfs-command]]
+== Executing the `vagrant sshfs` Command
+
+The Vagrant SSHFS plugin also supports execution of the `vagrant sshfs`
+command from the command line. Executing this command with the `--mount`
+option will iterate through the Vagrant file and attempt to mount (via
+SSHFS) any folders that aren't already mounted in the Vagrant guest.
+Executing with the `--unmount` option will unmount any mounted folders.
+
+....
+vagrant sshfs [--mount|--unmount] [vm-name]
+....
+
+[[options]]
+== Options
+
+The SSHFS synced folder plugin supports a few options that can be
+provided in the `Vagrantfile`. The following sections describe the
+options in more detail.
+
+[[generic-options]]
+=== Generic Options
+
+The SSHFS synced folder plugin supports a few options that can be
+provided in the `Vagrantfile`. They are described below:
+
+* `disabled`
+** If set to 'true', ignore this folder and don't mount it.
+* `ssh_opts_append`
+** Add some options for the ssh connection that will be established.
+** See the ssh man page for more details on possible options.
+* `sshfs_opts_append`
+** Add some options for the sshfs fuse mount that will made
+** See the sshfs man page for more details on possible options.
+
+An example snippet from a `Vagrantfile`:
+
+....
+config.vm.synced_folder "/path/on/host", "/path/on/guest",
+    ssh_opts_append: "-o Compression=yes -o CompressionLevel=5",
+    sshfs_opts_append: "-o auto_cache -o cache_timeout=115200",
+    disabled: false, type: "sshfs"
+....
+
+[[options-specific-to-arbitrary-host-mounting]]
+=== Options Specific to Arbitrary Host Mounting
+
+The following options are only to be used when
+link:#sharing-arbitrary-host-directory-to-vagrant-guest---1-of-users[sharing
+an arbitrary host directory] with the guest. They will be ignored
+otherwise:
+
+* `ssh_host`
+** The host to connect to via SSH. If not provided this will be detected
+as the Vagrant host that is running the Vagrant guest.
+* `ssh_port`
+** The port to use when connecting. Defaults to port 22.
+* `ssh_username`
+** The username to use when connecting. If not provided it is detected
+as the current user who is interacting with Vagrant.
+* `ssh_password`
+** The password to use when connecting. If not provided and the user is
+not using SSH keys, then the user will be prompted for the password.
+Please use SSH keys and don't use this option!
+* `prompt_for_password`
+** The user can force Vagrant to interactively prompt the user for a
+password by setting this to 'true'. Alternatively the user can deny
+Vagrant from ever prompting for the password by setting this to 'false'.
+
+An example snippet from a `Vagrantfile`:
+
+....
+config.vm.synced_folder "/path/on/host", "/path/on/guest",
+    ssh_host: "somehost.com", ssh_username: "fedora",
+    ssh_opts_append: "-o Compression=yes -o CompressionLevel=5",
+    sshfs_opts_append: "-o auto_cache -o cache_timeout=115200",
+    disabled: false, type: "sshfs"
+....
+
+[[options-specific-to-reverse-mounting-guest-host-mount]]
+=== Options Specific to Reverse Mounting (Guest->Host Mount)
+
+If your host has the `sshfs` software installed then the following
+options enable mounting a folder from a Vagrant Guest into the Vagrant
+Host:
+
+* `reverse`
+** This can be set to 'true' to enable reverse mounting a guest folder
+into the Vagrant host.
+
+An example snippet from a `Vagrantfile` where we want to mount `/data`
+on the guest into `/guest/data` on the host:
+
+....
+config.vm.synced_folder "/guest/data", "/data", type: 'sshfs', reverse: true
+....
+
+[[faq]]
+== FAQ
+
+Here are some answers to some frequently asked questions:
+
+[[why-do-new-files-take-time-to-appear-inside-the-guest]]
+=== Why do new files take time to appear inside the guest?
+
+Sometimes it can take time for files to appear on the other end of the
+sshfs mount. An example would be I create a file on my host system and
+then it doesn't show up inside the guest mount for 10 to 20 seconds.
+This is because of caching that SSHFS does to improve performance.
+Performance vs accuracy is always going to be a trade-off. If you'd like
+to disable caching completely you can disable caching completely by
+appending the `cache=no` SSHFS option to the synced folder definition in
+the Vagrantfile like so:
+
+....
+config.vm.synced_folder "/path/on/host", "/path/on/guest",
+    type: "sshfs", sshfs_opts_append: "-o cache=no"
+....
+
+All caching options that are available to sshfs can be added/modified in
+this same manner.
+
+[[appendix-a-using-keys-and-forwarding-ssh-agent]]
+== Appendix A: Using Keys and Forwarding SSH Agent
+
+When
+link:#sharing-arbitrary-host-directory-to-vagrant-guest---1-of-users[sharing
+an arbitrary host directory] you may want a completely non-interactive
+experience. You can either hard code your password in the Vagrantfile or
+you can use SSH keys. A few guides for setting up ssh keys and key
+forwarding are on Github: 
+
+* https://help.github.com/articles/generating-ssh-keys[Key Generation]
+* https://developer.github.com/guides/using-ssh-agent-forwarding/[Key Forwarding]
+
+The idea is that if `key1` is a key that is authorized to log in to the
+Vagrant host ,meaning there is an entry for `key1` in the
+`~/.ssh/authorized_keys` file, then you should be able to do the
+following to have a non-interactive experience with SSH keys and agent
+forwarding:
+
+Modify the Vagrantfile to forward your SSH agent:
+
+....
+config.ssh.forward_agent = 'true'
+....
+
+Now set up your agent and add your key to the agent:
+
+....
+# eval $(ssh-agent)
+# ssh-add /path/to/key1
+....
+
+And finally bring up your Vagrant guest:
+
+....
+# vagrant up
+....
+
+[[appendix-b-development]]
+== Appendix B: Development
+
+For local development of this plugin here is an example of how to build,
+test and install this plugin on your local machine:
+
+....
+# Install development dependencies
+$ gem install bundler && bundle install
+
+# List available Rake tasks
+$ bundle exec rake -T
+
+# Run Cucumber tests
+$ bundle exec rake featuretests
+
+# Build the gem (gets generated in the 'pkg' directory
+$ bundle exec rake build
+
+# Run Vagrant in the context of the plugin
+$ bundle exec vagrant <command>
+
+# Install built gem into global Vagrant installation (run outside of git checkout!)
+$ vagrant plugin install <path to gem in pkg directory>
+....

data/RELEASE.txt

@@ -0,0 +1,39 @@
+
+Make sure to bump version and commit
+
+Install git-evtag
+
+git-evtag sign v1.2.0
+
+-> In vim add thanks to contributors - grab info with
+   git log --no-merges --pretty=format:"%h - %an - %s"
+   and
+   git log --no-merges --pretty=format:"%h - %ae - %s"
+   
+
+-> In vim add commit log - grab with 
+   git log --no-merges --pretty=format:"%h %s"
+
+-> In vim add release message - see previous tag for example
+
+close and type in password for signing
+
+verify with git-evtag verify v1.2.0
+verify with git verify-tag v1.2.0 
+
+git push
+git push --tags 
+
+# Build with bundle exec rake build (inside viv VM)
+bundle exec rake build
+
+# Sign the output
+gpg --armor --detach-sign pkg/vagrant-sshfs-1.2.0.gem
+$ ls pkg/vagrant-sshfs-1.2.0.gem* 
+pkg/vagrant-sshfs-1.2.0.gem  pkg/vagrant-sshfs-1.2.0.gem.asc
+
+# Update release notes and upload files on github
+
+# push to rubygems with:
+gem push pkg/vagrant-sshfs-1.2.0.gem
+

data/lib/vagrant-sshfs/cap/guest/linux/sshfs_forward_mount.rb

@@ -176,10 +176,11 @@ module VagrantPlugins
           sshfs_cmd+= sshfs_opts + ' ' + sshfs_opts_append + ' '
 
           # The ssh command to connect to guest and then launch sshfs
+          # Note the backslash escapes for IdentityFile - handles spaces in key path
           ssh_opts = opts[:ssh_opts]
           ssh_opts+= ' -o User=' + machine.ssh_info[:username]
           ssh_opts+= ' -o Port=' + machine.ssh_info[:port].to_s
-          ssh_opts+= ' -o IdentityFile=' + machine.ssh_info[:private_key_path][0]
+          ssh_opts+= ' -o "IdentityFile=\"' + machine.ssh_info[:private_key_path][0] + '\""'
           ssh_opts+= ' -o UserKnownHostsFile=/dev/null '
           ssh_opts+= ' -F /dev/null ' # Don't pick up options from user's config
           ssh_cmd = ssh_path + ssh_opts + ' ' + ssh_opts_append + ' ' + machine.ssh_info[:host]

data/lib/vagrant-sshfs/cap/host/linux/sshfs_reverse_mount.rb

@@ -75,9 +75,10 @@ module VagrantPlugins
           opts[:ssh_opts]+= ' -o ServerAliveInterval=30 '  # send keepalives
 
           # SSH connection options
+          # Note the backslash escapes for IdentityFile - handles spaces in key path
           ssh_opts = opts[:ssh_opts]
           ssh_opts+= ' -o Port=' + machine.ssh_info[:port].to_s
-          ssh_opts+= ' -o IdentityFile=' + machine.ssh_info[:private_key_path][0]
+          ssh_opts+= ' -o "IdentityFile=\"' + machine.ssh_info[:private_key_path][0] + '\""'
           ssh_opts+= ' -o UserKnownHostsFile=/dev/null '
           ssh_opts+= ' -F /dev/null ' # Don't pick up options from user's config
 

data/lib/vagrant-sshfs/version.rb

@@ -1,5 +1,5 @@
 module VagrantPlugins
   module SyncedFolderSSHFS
-    VERSION = "1.2.0"
+    VERSION = "1.2.1"
   end
 end

data/test/libvirt/README.txt

@@ -11,5 +11,10 @@ and then:
 
 cd /sharedfolder/code/github.com/dustymabe/vagrant-sshfs/
 gem install bundler
-bundle install
+bundle install --with plugins # see [1]
 bundle exec rake featuretests
+
+[1] when running with bundler 1.13.2 I had to comment out
+    the vagrant-sshfs line in Gemfile because it errored out
+    complaining about it being defined twice. Running with
+    1.12.5 works fine.

data/test/virtualbox/README.txt

@@ -13,5 +13,10 @@ and then:
 
 cd /sharedfolder/code/github.com/dustymabe/vagrant-sshfs/
 gem install bundler
-bundle install
+bundle install --with plugins # see [1]
 bundle exec rake featuretests
+
+[1] when running with bundler 1.13.2 I had to comment out
+    the vagrant-sshfs line in Gemfile because it errored out
+    complaining about it being defined twice. Running with
+    1.12.5 works fine.

metadata

@@ -1,14 +1,14 @@
 --- !ruby/object:Gem::Specification
 name: vagrant-sshfs
 version: !ruby/object:Gem::Version
-  version: 1.2.0
+  version: 1.2.1
 platform: ruby
 authors:
 - Dusty Mabe
 autorequire: 
 bindir: bin
 cert_chain: []
-date: 2016-08-08 00:00:00.000000000 Z
+date: 2016-11-11 00:00:00.000000000 Z
 dependencies:
 - !ruby/object:Gem::Dependency
   name: win32-process
@@ -105,7 +105,8 @@ files:
 - ".gitignore"
 - Gemfile
 - LICENSE
-- README.md
+- README.adoc
+- RELEASE.txt
 - Rakefile
 - features/README.md
 - features/sshfs_cwd_mount.feature

data/README.md

@@ -1,271 +0,0 @@
-# vagrant-sshfs
-
-This is a vagrant plugin that adds synced folder support for mounting
-folders from the Vagrant host into the Vagrant guest via
-[SSHFS](https://github.com/libfuse/sshfs). In the default mode it does 
-this by executing the `SSHFS` client software within the guest, which 
-creates an SSH connection from the Vagrant guest back to the Vagrant host. 
-
-The benefits of this approach:
-- Works on any host platform and hypervisor type
-    - Windows, Linux, Mac OS X
-    - Virtualbox, Libvirt, Hyper-V, VMWare
-- Seamlessly works on remote Vagrant solutions
-    - Works with vagrant aws/openstack/etc.. plugins
-
-The drawbacks with this approach:
-- Performance is worse than an implementation like NFS
-- There must be `sftp-server` software on the Vagrant host 
-
-`sftp-server` is usually provided by SSH server software so it already
-exists on Linux/Mac. On windows you only need to install
-[openssh](https://cygwin.com/cgi-bin2/package-cat.cgi?file=x86_64%2Fopenssh%2Fopenssh-7.2p1-1&grep=openssh)
-via [cygwin](https://cygwin.com/) and you will get `sftp-server`.
-
-## History
-
-The inspiration for this plugin came from [Fabio Kreusch](https://github.com/fabiokr)
-and his [code](https://github.com/fabiokr/vagrant-sshfs) for the original 
-vagrant-sshfs Vagrant plugin. The goal of this plugin (as opposed to
-the old implementation) is to implement SSHFS as a synced folder
-plugin just like the other synced folder plugins (NFS/RSYNC/SMB/VirtualBox).
-
-This plugin was developed mainly by copying the code from the NFS synced 
-folder plugin from the Vagrant core code and molding it to fit SSHFS.
-
-## Modes of Operation
-
-### Sharing Vagrant Host Directory to Vagrant Guest - 98% of users
-
-This plugin uses SSHFS slave mounts 
-(see [link](https://github.com/dustymabe/vagrant-sshfs/issues/11))
-to mount a directory from the Vagrant Host into the Vagrant Guest. It
-uses the `sftp-server` software that exists on the host and `sshfs`
-running in *slave mode* within the guest to create a connection using
-the existing authentication over SSH that vagrant sets up for you.
-
-### Sharing Arbitrary Host Directory to Vagrant Guest - 1% of users
-
-This plugin allows you to share a folder from an arbitrary host to the
-Vagrant Guest. This would allow you to do a folder mount to some other
-host that may have files that you need. To do this the plugin will run
-an SSHFS command from the Guest and connect to the arbitrary host that
-must have an SSH daemon running. You must provide the `ssh_host`
-option in the Vagrantfile to get this to work. You can use ssh key
-forwarding or username/password for authentication for this.
-
-See [Options](#options-specific-to-arbitrary-host-mounting) and 
-[Appendix A](#appendix-a-using-keys-and-forwarding-ssh-agent) for
-more information.
-
-### Sharing Vagrant Guest Directory to Vagrant Host - 1% of users
-
-*NOTE:* This option is dangerous as data will be destroyed upon `vagrant destroy`
-
-This plugin allows you to share a folder from a Vagrant guest into the
-host. If you have workloads where there are a lot of disk intensive
-operations (such as compilation) it may be ideal to have the files
-live in the guest where the disk intensive operations would occur.
-For discussion see [Issue #7](https://github.com/dustymabe/vagrant-sshfs/issues/7).
-
-See [Options](#options-specific-to-reverse-mounting-guest-host-mount)
-for more information on how to enable this type of mount.
-
-## Getting Started
-
-In order to use this synced folder implementation perform the
-following steps:
-
-### Install Plugin
-
-In order to install the plugin simply run the following command:
-
-```
-# vagrant plugin install vagrant-sshfs
-```
-
-### Add SSHFS Synced Folder in Vagrantfile
-
-Edit your Vagrantfile to specify a folder to mount from the host into
-the guest:
-
-```
-config.vm.synced_folder "/path/on/host", "/path/on/guest", type: "sshfs"
-```
-
-Now you can simply `vagrant up` and your folder should be mounted in
-the guest. For more options that you can add see the [Options](#options) 
-section.
-
-## Executing the `vagrant sshfs` Command
-
-The Vagrant SSHFS plugin also supports execution of the `vagrant sshfs`
-command from the command line. Executing this command with the `--mount`
-option will iterate through the Vagrant file and attempt to mount (via 
-SSHFS) any folders that aren't already mounted in the Vagrant guest.
-Executing with the `--unmount` option will unmount any mounted folders.
-
-```
-vagrant sshfs [--mount|--unmount] [vm-name]
-```
-
-## Options
-
-The SSHFS synced folder plugin supports a few options that can be
-provided in the `Vagrantfile`. The following sections describe the
-options in more detail.
-
-### Generic Options
-
-The SSHFS synced folder plugin supports a few options that can be
-provided in the `Vagrantfile`. They are described below:
-
-- `disabled`
-    - If set to 'true', ignore this folder and don't mount it.
-- `ssh_opts_append`
-    - Add some options for the ssh connection that will be established.
-    - See the ssh man page for more details on possible options.
-- `sshfs_opts_append`
-    - Add some options for the sshfs fuse mount that will made
-    - See the sshfs man page for more details on possible options.
-
-An example snippet from a `Vagrantfile`:
-
-```
-config.vm.synced_folder "/path/on/host", "/path/on/guest",
-    ssh_opts_append: "-o Compression=yes -o CompressionLevel=5",
-    sshfs_opts_append: "-o auto_cache -o cache_timeout=115200",
-    disabled: false, type: "sshfs"
-```
-
-### Options Specific to Arbitrary Host Mounting
-
-The following options are only to be used when
-[sharing an arbitrary host directory](#sharing-arbitrary-host-directory-to-vagrant-guest---1-of-users)
-with the guest. They will be ignored otherwise:
-
-- `ssh_host`
-    - The host to connect to via SSH. If not provided this will be 
-      detected as the Vagrant host that is running the Vagrant guest.
-- `ssh_port`
-    - The port to use when connecting. Defaults to port 22.
-- `ssh_username`
-    - The username to use when connecting. If not provided it is
-    detected as the current user who is interacting with Vagrant.
-- `ssh_password`
-    - The password to use when connecting. If not provided and the
-      user is not using SSH keys, then the user will be prompted for
-      the password. Please use SSH keys and don't use this option!
-- `prompt_for_password`
-    - The user can force Vagrant to interactively prompt the user for
-      a password by setting this to 'true'. Alternatively the user can
-      deny Vagrant from ever prompting for the password by setting
-      this to 'false'.
-
-An example snippet from a `Vagrantfile`:
-
-```
-config.vm.synced_folder "/path/on/host", "/path/on/guest",
-    ssh_host: "somehost.com", ssh_username: "fedora",
-    ssh_opts_append: "-o Compression=yes -o CompressionLevel=5",
-    sshfs_opts_append: "-o auto_cache -o cache_timeout=115200",
-    disabled: false, type: "sshfs"
-```
-
-### Options Specific to Reverse Mounting (Guest->Host Mount)
-
-If your host has the `sshfs` software installed then the following 
-options enable mounting a folder from a Vagrant Guest into the 
-Vagrant Host:
-
-- `reverse`
-    - This can be set to 'true' to enable reverse mounting a guest
-      folder into the Vagrant host.
-
-An example snippet from a `Vagrantfile` where we want to mount `/data`
-on the guest into `/guest/data` on the host:
-
-```
-config.vm.synced_folder "/guest/data", "/data", type: 'sshfs', reverse: true
-```
-
-## FAQ
-
-Here are some answers to some frequently asked questions:
-
-### Why do new files take time to appear inside the guest?
-
-Sometimes it can take time for files to appear on the other end of the
-sshfs mount. An example would be I create a file on my host system and
-then it doesn't show up inside the guest mount for 10 to 20 seconds.
-This is because of caching that SSHFS does to improve performance.
-Performance vs accuracy is always going to be a trade-off. If you'd
-like to disable caching completely you can disable caching completely
-by appending the `cache=no` SSHFS option to the synced folder
-definition in the Vagrantfile like so:
-
-```
-config.vm.synced_folder "/path/on/host", "/path/on/guest",
-    type: "sshfs", sshfs_opts_append: "-o cache=no"
-```
-
-All caching options that are available to sshfs can be added/modified
-in this same manner.
-
-## Appendix A: Using Keys and Forwarding SSH Agent
-
-When [sharing an arbitrary host directory](#sharing-arbitrary-host-directory-to-vagrant-guest---1-of-users)
-you may want a completely non-interactive experience. You can either
-hard code your password in the Vagrantfile or you can use SSH keys.
-A few guides for setting up ssh keys and key forwarding are on Github:
-- [Key Generation](https://help.github.com/articles/generating-ssh-keys)
-- [Key Forwarding](https://developer.github.com/guides/using-ssh-agent-forwarding/)
-
-The idea is that if `key1` is a key that is authorized to log in to the 
-Vagrant host ,meaning there is an entry for `key1` in the `~/.ssh/authorized_keys` 
-file, then you should be able to do the following to have a
-non-interactive experience with SSH keys and agent forwarding:
-
-Modify the Vagrantfile to forward your SSH agent:
-
-```
-config.ssh.forward_agent = 'true'
-```
-
-Now set up your agent and add your key to the agent:
-
-```
-# eval $(ssh-agent)
-# ssh-add /path/to/key1
-```
-
-And finally bring up your Vagrant guest:
-
-```
-# vagrant up
-```
-
-
-## Appendix B: Development
-
-For local development of this plugin here is an example of how to build, test and install this plugin on your local machine:
-
-```
-# Install development dependencies
-$ gem install bundler && bundle install
-
-# List available Rake tasks
-$ bundle exec rake -T
-
-# Run Cucumber tests
-$ bundle exec rake featuretests
-
-# Build the gem (gets generated in the 'pkg' directory
-$ bundle exec rake build
-
-# Run Vagrant in the context of the plugin
-$ bundle exec vagrant <command>
-
-# Install built gem into global Vagrant installation (run outside of git checkout!)
-$ vagrant plugin install <path to gem in pkg directory>
-```