Mastodawn

Caspar Green 👻Apr 18, 2023

Is anyone else experiencing an issue where #PHPStorm takes 30-60sec to save files when working in a #WSL (wsl2/windows 10) project?

This issue seems to have started for me after a Windows update last week.

I have Storm installed on Windows. Tried installing Storm also directly on WSL (Ubuntu) and that seems to work for saving, but because of other things makes XDebug inaccessible. (╯’□’)╯︵ ┻━┻

Show thread

Derick Rethans Apr 18, 2023

@iCaspar You can make Xdebug work there, I believe by setting xdebug.client_host=localhost — if that doesn't work, try xdebug://nameserver — and if that doesn't work, make a log (xdebug.log_level=11 + xdebug.log=/tmp/xdebug.log) and show it to me 🙂

Show thread

Caspar Green 👻Apr 18, 2023

@derickr Thanks for this.

I'll give that a go.

The project is actually running inside a highly customized #Lando (wrapper for #docker) container running inside #wsl

There is some info about it here: https://docs.lando.dev/guides/setup-lando-on-windows-with-wsl-2.html#configure-host-ip
But our lando things are customized to the point where this does not work "out of the box".

(With Storm running on the Windows side, using host.docker.internal:host-gateway under extra_hosts in the .lando.yml works fine.)

Setup Lando on Windows with WSL2

Configure Lando to run on your Windows WSL2 system for better performance when developing on Windows.

Lando

Show thread

Derick Rethans

@iCaspar You don't have to add that line anymore with Xdebug 3.2 either - you can set:

xdebug.client_host=xdebug://gateway