ifconfig does not show any such address however. My host IP adress via DHCP is 192.168.a.z. whatever. diffrent (edited)

"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'"

well at the moment i use the updated version an translated the config manual from dutch. On installation I get IP conflict: (edited)

@deschebbs, if you need any help, please ask. It has options, but they are sort of hidden in config files or "need to know"... (edited)

thanks folks, i keep that in mind. Still trying on twisted.

And being on a windows host, things like NFS (or folder sharing in general) is a waste of time, so I just don't.

NFS didn't work for you? We use NFS shares pretty successfully. 🤔

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.

And the realisation that it only works properly if you start Vagrant (and the associated winnfsd process) in an Administrator command prompt.

How do you find things like yarn watch on an NFS mount? (edited)

We use essentially the same Vagrantfile in an office of 5-6 devs, and most of the time we forget about it.

MS's support for WSL is getting better, so maybe I'll give it a better shot again some time soon (when I have time)

The network share part of our Vagrantfile looks like this:

  1. # share additional folders to the guest VM
  2. host_root = '/workspace/sites' # host folder containing your websites
  3. if is_windows
  4. # use NFS shares to drastically improve performance (options avoid locking issues)
  5. nfs_options = ['vers=3', :udp, :nolock, :noatime,'actimeo=1']
  6. config.vm.synced_folder host_root, '/var/www/html', type: :nfs, mount_options: nfs_options
  7. else
  8. config.vm.synced_folder host_root, '/var/www/html',
  9. id: "vagrant-root",
  10. owner: "vagrant",
  11. group: "www-data",
  12. mount_options: ["dmode=775"]
👍 (1)

wow nice, ta. What do you use for providing NFS on windows?

oh, yeah I'm pretty sure I tried that and found it extremely unstable.

More because I use a single box for general purpose dev, and specific ones for targetted testing.