I think for "auto configuration" you would need a PHPStorm plugin that is able to parse everything inside. This seems to work for non WSL environments already and as you can see in the video in the PHPStorm ticket, it also works for relative paths in WSL. I hoped using the docker-compose-full file and configuring phpstorm once per project would work.
If you work in a team every team member wpuld need to do those steps for each project they work on.Įven if you automate these steps in a script if feels strange and not well integrated. update the dumped docker-compose file regulary, as the configuration might change (I think?).configure remote interpreter (which is also quite complicated instead of the auto configures vagrant stuff).replace port definitions (fixed in 2021.2).remove debugging output from the first line.I know it is already possible, but the way to achieve this is currently quite complicated and especially for "newbies" very difficult. Means I run ddev start and afterwards I want to be able to use all the phpstorm features that are availabe for vagrant environments, like running single tests by clicking the play button beside their definition, or debugging code in cli environment. I would like to accomplish a "vagrant like" setup.
0 kommentar(er)
