Closed johannesboyne closed 10 years ago
Glad to see it please you but Vagrant only exists in 1.x version for now.
Changes made for Vagrant 1.0 in the plugin API are supported since vagrant-bindfs 0.2 thanks to igor47's work and it won't break unless some major change occured in the Vagrant codebase as the plugin API is supposed to be backward-compatible.
Or did I miss something in your question ?
Mhhh.... the naming is confusing, the docs say v2
http://docs.vagrantup.com/v2/
but it's true, I am talking about Vagrant version 1.2.3
I am asking, because share_folder are synced_folder now and the underlying api may has changed.
http://docs.vagrantup.com/v2/synced-folders/index.html
But I am not 100% sure, I am just using vagrant and I've not looked into the source.
Thanks for you quick reply!
so, my question is: how to map this "new" config.
Vagrant.configure("2") do |config|
# ...
config.vm.synced_folder "src/", "/srv/website"
end
with this one:
# Complete example for a NFS shared folder
config.vm.network :hostonly, "33.33.33.10" # (required to use NFS shared folder)
config.vm.share_folder "nfs-share", "/vagrant-nfs", "host/source/dir", :nfs => true
config.bindfs.bind_folder "/vagrant-nfs", "guest/mount/point"
vagrant-bindfs is not tied to the Vagrant shared folders API as you can bind any folder, shared or not, in the guest machine to another location. This change should not affect the plugin.
The full documentation for NFS shared folders with Vagrant is available here.
I'll update the README soon.
I'm getting this error with vagrant 1.4:
Bringing machine 'default' up with 'virtualbox' provider...
/Users/miguel/.vagrant.d/gems/gems/vagrant-bindfs-0.2.2/lib/vagrant-bindfs/plugin.rb:28:in `block (2 levels) in <class:Plugin>': uninitialized constant Vagrant::Action::Builtin::NFS (NameError)
from /Applications/Vagrant/embedded/gems/gems/vagrant-1.4.0/lib/vagrant/action/runner.rb:45:in `call'
from /Applications/Vagrant/embedded/gems/gems/vagrant-1.4.0/lib/vagrant/action/runner.rb:45:in `block (2 levels) in run'
from /Applications/Vagrant/embedded/gems/gems/vagrant-1.4.0/lib/vagrant/action/runner.rb:44:in `tap'
from /Applications/Vagrant/embedded/gems/gems/vagrant-1.4.0/lib/vagrant/action/runner.rb:44:in `block in run'
from /Applications/Vagrant/embedded/gems/gems/vagrant-1.4.0/lib/vagrant/action/runner.rb:43:in `map'
from /Applications/Vagrant/embedded/gems/gems/vagrant-1.4.0/lib/vagrant/action/runner.rb:43:in `run'
from /Applications/Vagrant/embedded/gems/gems/vagrant-1.4.0/lib/vagrant/machine.rb:147:in `action'
from /Applications/Vagrant/embedded/gems/gems/vagrant-1.4.0/lib/vagrant/batch_action.rb:63:in `block (2 levels) in run'
from /Users/miguel/.vagrant.d/gems/gems/logging-1.8.1/lib/logging/diagnostic_context.rb:323:in `call'
from /Users/miguel/.vagrant.d/gems/gems/logging-1.8.1/lib/logging/diagnostic_context.rb:323:in `block in create_with_logging_context'
I dont know if it's related with this question
Vagrant 1.4 changes the way it handles NFS share. I'll try to fix vagrant-bindfs tomorrow.
Subscribing to this issue, as I have the same problem. Thanks for the work on the update.
I'm also getting this error message. Let me know if I can be of any help.
Also seeing this issue.
vagrant-bindfs can now be used with Vagrant 1.4 (and is still compatible with older versions). See issue #10 for details.
Just run vagrant plugin update vagrant-bindfs
to update to the new release.
1st: great plugin!
Q: Is a vagrant version 2 support planned?