LAMP stack in the Windows Subsystem for Linux

In the search for the optimal development environment, Windows 10 offers not only complete solutions such as XAMPP, WAMP and MAMP, a native installation by hand, but also virtualization solutions such as Vagrant(Scotch Box) and Docker(Devil Box, Laradock), but all solutions failed - except for one - due to my requirements such as free configurability, real wildcard SSL certificates, access from all end devices in the local network, and high stability and performance.


I've been experimenting with all variants (especially Docker) for the last few months and got stuck with Lando, but it turned out that all Docker (and Vagrant) based solutions don't work for performance reasons on Windows and Mac for projects with a higher number of files (one page view took about 25 seconds). There are numerous threads here and here and here where the cause and possible solutions are discussed.

For me there were too many pills to swallow - files shouldn't be synchronized manually, but simply be available. I also didn't want to go back to the MAMP PRO that I had been using for years (especially a horror under Windows). So I went back to the beginning and tried again natively. Under Windows this was an outrageous undertaking in the normal way or via Cygwin , until I tried WSL .

I had already had very positive experiences with the Windows Subsystem for Linux in recent months and after all LAMP services worked after a short test without restrictions in terms of stability and performance, I came to the conclusion that Microsoft has achieved great things here. This is followed by my (constantly expanding) setup including all scripts for my current development environment under Windows 10 Pro:

3d95982c87ac786700b6d602cd977234

3d95982c87ac786700b6d602cd977234

3d95982c87ac786700b6d602cd977234

Back