This blog is to help me remember what I have done, hopefully teach others and get feedback and learn from others. 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. The setup can be found in this repository. 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. Once you understand the set up, it will probably soon be your favorite Laravel dev environment as well. With Xdebug 3, we can use xdebuginfo() to check what config Xdebug is using.
However, what I am showing to day is actually more perfomant. 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. In my last post I showed how you can set up XDebug for a simple dev environment, which used php artisan serve. Latest Release Xdebug 3.2.1 Release date: Linux, macOS: source Windows binaries: PHP 8.0 VS16 (64 bit) PHP 8.0 VS16 TS (64 bit) PHP 8.1 VS16 (64 bit) PHP 8.1 VS16 TS (64 bit) PHP 8.2 VS16 (64 bit) PHP 8. docker/xdebug.ini /usr/local/etc/php/conf.d/xdebug.iniĪnd I have modified my VScode launch.With Xdebug 3, we can use xdebug_info() to check what config Xdebug is using. # Copy xdebug configration for remote debuggingĬOPY. I have added this in my windows laravel folder /docker/8.0/Dockerfile ARG INSTALL_XDEBUG=true I have added in my windows laravel folder /docker/8.0/php.ini It is good that Sail manages everything for me! But I would like to allow the debugging in VSCode.
0 kommentar(er)
