![]() If you start installing all your software inside the WSL what are you using Windows for? Just to run Teams and Office Applications? ) But this is another offtopic discussion I think. For private use, running PHPStorm in WSL might be the better decission. Running ddev start and using the browser to access your project is very simple and great, but you want features like CLI Debugging, GUI for test execution and result visualization and other stuff PHPStorm offers as well of course.Īctually, JetBrains is very happy to have people running their tools inside WSL2 because they get 1000 less complaints per day :) To use it in company it has to be more simple to integrate in PHPStorm so you can let a junior dev checkout a project and start working without much knowledge about docker / ddev / PHPStorm. I already work with this setup for smaller private projects and I am very happy with all the features ddev offers and how simple it is to use.īut I would like to use it also in our company. Also the wsl indexing performance of PHPStorm was improved a lot with the last update by, so I am quite happy with my setup. This combines a good usability of PHPStorm in my windows environment and a good performance of my application since WSL -> docker does not need a nfs share or anything like that. Currently I have PHPStorm installed on Windows, my project is located in WSL. ddev as there should be all information needed to configure a remote interpeter, ssh sessions and so on but sadly I do not know anyone who is able to write such a plugin. 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 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |