In Gabriel's guide (http://goo.gl/clpKa) on this page, he found a workaround that is implemented in both Vagrant solutions featured here.
Essentially the directory for things like the NPM modules and the MongoDB database files would be a mount --bind symlink. This in concert with the Vagrant / VirtualBox flag:
config.vm.provider "virtualbox" do |v|
v.customize ["setextradata", :id, "VBoxInternal2/SharedFoldersEnableSymlinksCreate/vagrant-root", "1"]
end
I don't think either of us could get this to work when putting this in fstab because Vagrant also has things in fstab and so the VM wouldn't boot, but in my case Chef handles the creation of these on boot, and in Gabriel's he recommends putting the command in the mount --bing in the .bashrc
Essentially the directory for things like the NPM modules and the MongoDB database files would be a mount --bind symlink. This in concert with the Vagrant / VirtualBox flag:
My Meteor Chef recipe automates the binding of these using the Chef "mount" resource and is around line 89 of the chef recipe: https://github.com/shoebappa/vagrant-meteor-windows/blob/mas...I don't think either of us could get this to work when putting this in fstab because Vagrant also has things in fstab and so the VM wouldn't boot, but in my case Chef handles the creation of these on boot, and in Gabriel's he recommends putting the command in the mount --bing in the .bashrc