Message of the day:
A virtual pony is still a pony
All things virtual
"Bringing machine 'twistedbytes-site.blah' up with 'virtualbox' provider... ==> twistedbytes-site.blah: Checking if box 'twistedbytes/webserver' is up to date... ==> twistedbytes-site.blah: Clearing any previously set network interfaces... The specified host network collides with a non-hostonly network! This will cause your specified IP to be inaccessible. Please change the IP or name of your host only network so that it no longer matches that of a bridged or non-hostonly network.
Bridged Network Address: '192.168.xx.y' Host-only Network 'eth0': '192.168.xx.y'"
And being on a windows host, things like NFS (or folder sharing in general) is a waste of time, so I just don't.
But it's more of a thing with (internet made) system expectations of a particular feature level of the file system, checked by OS, not by what is mounted (ie. pure assumption). E.g. a load of node modules failing to install because symlinks can't be made.
The network share part of our Vagrantfile looks like this:
- # share additional folders to the guest VM
- host_root = '/workspace/sites' # host folder containing your websites
- if is_windows
- # use NFS shares to drastically improve performance (options avoid locking issues)
- nfs_options = ['vers=3', :udp, :nolock, :noatime,'actimeo=1']
- config.vm.synced_folder host_root, '/var/www/html', type: :nfs, mount_options: nfs_options
- config.vm.synced_folder host_root, '/var/www/html',
- id: "vagrant-root",
- owner: "vagrant",
- group: "www-data",
- mount_options: ["dmode=775"]