This works on Windows, but crashes on OS X with a number of errors telling us that the symlink has no referent (one error per symbolic link). Instead of using a standard shared folder we now have tried using the rsync type.So far, we haven’t found a way of running code in the Vagrantfile depending on the provider used. There is a workaround mentioned in an issue of Vagrant, unfortunately this is VirtualBox-only and does not help those who run VMware.So far, we have tried a number of options: The only thing that we can not do is get rid of the symbolic links, so we need another way to deal with this.
Inside of our source code we actually do have a few symbolic links, which is not a problem within the Linux inside the VM, but on Windows as host this causes problems. This basically, works as well … except for symbolic links. Now our idea was that each developer shall be able use the IDE of their choice, and hence we have introduced a synced folder that shares the source code between the host and the VM. Some use OS X, some Linux, and some Windows.I want to use Vagrant to provide a common development environment to my team.
0 kommentar(er)
