-
-
Notifications
You must be signed in to change notification settings - Fork 36
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Remove install instructions for Vagrant #33
Comments
@PAStheLoD I don't use Vagrant myself, but have you tried the plugin vagrant-winnfsd? |
Hello! Thanks for the quick reply! I haven't tried NFS in this case (but when I tried it with a Python project a few months ago, and basically the same result - just a matter of time before something comes up). So in general I found that with great tools like scoop for Windows it's easy to get a sort of reliable dev env setup going. (And just use Vagrant for the DB and other backing services. Plus it's easy to script the host side setup via a bit of Ruby.) |
Until now, the only plan was to restructure the page for skeleton application and the different kinds of installations. But we will have to re-evaluate the tools to offer the best possible entry and choice. |
Bug Report
Summary
In case this is not the correct repository for report this bug, please help me find the right one. Thanks!
Basically the problem is that NTFS and ext4 and vboxsf doesn't really get along. (Symlink handling is an instant no-no, but even simple things like deleting files will cause problems, if for some reason the host side thinks that VirtualBox shouldn't be doing that. Maybe the file is open because VS Code saw a .git folder somewhere and thinks now is the time to index its contents.)
Current behavior
Following this tutorial: https://docs.laminas.dev/tutorials/getting-started/skeleton-application/
After vagrant up successfully completes running
$ vagrant ssh -c 'composer install'
leads to this error:I'd recommend documenting that Windows users should install WAMP and not try to use Vagrant, to avoid this dead-end. (Or solve the vboxsf issues, but I think VirtualBox devs are trying to come up for good solutions for these for about a decade.)
The text was updated successfully, but these errors were encountered: