Fast web development environment based on vagrant, perhaps?

Question

linux

I want to set up a development environment based on a normal lemp stack under linux and leave openserver, but I don’t want to leave windows.
I saw on the net that many people set up environments through vagrant, mount a folder with projects from windows in a linux system - but if you do it all through a virtual box, it turns out that everything works very slowly and this is due to the file system of the virtual box itself, there is a plugin that speeds up this whole thing - but the situation does not get much better.
Actually the question is: if you use vmware, will there be the same problems with the speed of the system, etc.?
PS - I need the folder with the project to be in windows, so working with the project via sftp is not a solution for me.

Answer 1

Vagrant is slow to start. If you have Windows 10, then you can install docker, it is much more convenient to use it.

Answer 2

Look at https://laravel.com/docs/5.8/homestead
Vagrant + configured environment + folder mapping between virtual machine and local machine + convenient configuration

Answer 3

You can connect the project directory via NFS, it will be faster.

Answer 4

Use WSL if you have Windows 10
Speed ​​at the system level and do not need to connect anything (folders, etc.) + a more flexible solution with the ability to configure anything and everything.

Answer 5

I tried to set up Vagrant at work, in the end I gave up on everything, put a clean server on the Ubuntu virtual machine, put what I need and the rules, I upload files via SFTP.
In general, you need to write in such a way that the code starts up on both Linux and Windows (the main thing is to keep the case in the paths)))).

Answer 6

WSL, which was advised here, is not needed - it's some kind of scrap.
I installed VMWare Workstation 15 for myself (you can use it for free), it works much faster than Virtualbox.
In VMWare, there is only one petty problem, you can’t assign the static IP you need without unnecessary picking.
Those. if VMWare assigned some 192.168.111.100 to your virtual machine, then you will have to use it.
Or you can buy this Workstation and there will already be normal tools for managing dhcp.
By the way, I have a docker in a virtual machine (consider a virtual machine in a virtual machine), so everything works without brakes and complaints