![]() env vars that you can use to change how XDebug works with Sail. ![]() Thank you to github user nhaynes for all of this. See for a brief discussion on these changes. Here's my interpretation (please correct me if I'm wrong).Īs of August, 2021, Laravel Sail now comes with the docker containers configured correctly for XDebug. I do seem to have xdebug running correctly on the server, but despite spending the day reading posts on how to make this happen I just can’t get phostorm to connect to xdebug.ĭoes anyone have step by step instructions on how to do this? It seems like this would be a good thing to have here or in the Sail documentation. I’m rather new to Laravel I’m loving it so far and making good progress on my project.īut, I’m having an awful time getting xdebug, sail, and phpstorm to play nice. This blog is to help me remember what I have done, hopefully teach others and get feedback and learn from others.Hello. You may be like me, having spent hours in StackOverflow trying to resolve issues with Xdebug and Chrome/ PHPStorm/ Docker.īut, after reading this article, you can see just how easy it is and start improving your local dev workflow, as well as improving performance bottlenecks before you get to production. Conclusionīecause Xdebug is way easier to use than it used to be, and the debugger/ profiler are invaluable tools for local development, I think this post adds a lot of value on top of the existing documentation. This is useful for checking your configuration has loaded correctly. env file and stop/ start Sail, you should see a page like the phpinfo() output. With Xdebug 3, we can use xdebug_info() to check what config Xdebug is using.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |