“attempt to debug every php script.” May not be preferable as it will slow down every call. To debug a postman/paw/api call use one of these methods to tell xdebug that you want to debug with the call: It seems like you can set a directory mapping at a higher level than the file is at and it will fix the mapping for all files within that directory, so you don’t need to do it for each individual file. When I connect to a new app I have to set the path mappings as my paths locally are different than the ones on the remote server. More importantly, if your files are not in sync your breakpoints might not break as they are set on lines that don’t have php code to execute on the remote server.
Even one line difference can be slightly confusing, although I have done that. Specifically the files you are going to debug needs to be exact, otherwise the breakpoint in your local code will still break there, but the variables and where the debugger steps to as you go from line to next line will be off and not make sense.
You need to have an exact copy of the codebase that you are going to debug on the remote server. I have an ssh profile file setup and use this for my connection: Host easyorthosandbox-qa-xdebug When you connect this way it’s simply going to open up a new connection in your terminal and then sit there. This sets up a way for your remote server to talk to your local computer. I’m just going to mention some specifics that aren’t listed in the PHPStorm docs or that I found particularly key. I used instructions found in the PHPStorm docs with the xdebug3 set of code.
0 kommentar(er)
