The new Windows terminal is an improved terminal announced by Microsoft at Build 2019. It drastically improves performance, as it no longer translates kernel calls, but rather runs in a micro-VM on top of Hyper-V.
WSL2 is the new version of WSL, available to only Windows insiders for now. WSL has brought a Linux kernel to Windows 10. WSL stands for the Windows Subsystem for Linux.
#Phpstorm wsl2 how to
In this post, I’ll walk you through how to setup WSL2, in combination with the (new) Windows Terminal and oh-my-zsh. I haven’t yet taken the time to re-setup my Linux setup on top of Windows 10.
#Phpstorm wsl2 windows 10
which you would have to change on each reboot) // this entries are to enhance ray by allowing to open the files directly in your editor 'remote_path' => $path_to_code_inside_wsl2, // usually something like /home/spatie/code/my-project 'local_path' => $path_to_code_to_wsl2_in_windows, // usually something like \\\\wsl$\\Ubuntu\\home\\spatie\\code\\my-project <- don't forget to escape the \ if using double-quotes like in the exampleĪlso note that you could run into issues with the Windows firewall or your antivirus software that could block the network communication between your WSL2 VM and your Windows 10 host, so check first if nothing is being blocked if you do not succeed at first to send ray debug events to the app.I recently re-imaged my laptop to a clean Windows 10. and 2.) or the WSL2 gateway IP address (3. In all of them what you need to do is set the following configuration in ray: 'host' => $windows_10_ip_addr, // this could be the windows 10 IP address (1. Reconfigure the ray package each time we boot our Windows 10 host and WSL2 to set $windows_10_ip_addr as the WSL2 gateway IP.Set a DHCP reservation for our Windows 10 host on our DHCP server.Set a static IP address manually for our Windows 10 host.The first two are the recommended ways as you are required to configure them only once: There are 3 ways to reach the ray app from within WSL2 that is running our code. First off we need to know that WSL2 changes its IP address segment on each launch (each Windows 10 reboot) because that's how it works in Hyper-V, but it also configures automatically the routing necessary to reach our physical network segment (Windows 10 IP address segment) from within WSL2 for us.
What we need to achieve is that WSL2 (which is running our code) is able to send the ray debug events to the Windows 10 host. Our Windows 10 host and our WSL2 Linux each have its own network configuration. Knowing this, we need to setup the ray package accordingly to connect to the app. When using WSL2 on Windows 10 we need to consider first how this technology works: essentially, the Linux running on WSL2, is an optimized VM running on Hyper-V, but it is a "full-blown" Linux OS independent from your host that has some specific kernel changes to make things a bit smoother.
#Phpstorm wsl2 update
However, be sure to update your run_editor.js to your current version of PhpStorm and everything should work. Problems getting it to work out of the box. There is aĬhance you may need to reference this issue if you are having Just goto PhpStorm Protocol Package and follow the directions. Windows 10 does not support the PhpStorm protocol and therefore you will not be able to open PhpStorm given the link from Ray.Īs a work-around, has a package to edits your registry to correlate the PhpStorm link protocol to your PhpStorm instance.
0 kommentar(er)
