On the EC2 instance, start running your program. The "Break" command means that once you run the CLI script on the Linux host, you should see that PHPStorm take you to the first line of your script and is now waiting for you to start stepping. In Run->Break in first line in PHP scripts In the PHPStorm IDE, click the telephone "listen" icon. In the Ide key(session id) field, put in phpstorm For me it's /home/ubuntu/code/JSON/process-JSON.php The field next to it will then have a "notepad" icon click that: "Absolute Path on the server".
Name: whatever you configured for "serverName" (aws in this example)Ĭlick on the php file you'll be debugging (in my case, process-JSON.php). Run->Edit Configurations->Defaults-> PHP Remote Debug Xdebug.var_display_max_children => 128 => 128 When xdebug remote debug is enabled and I enable debug listening in PHPStorm, it takes a short while to stop at the breakpoint, but not as slow as disabling phpstorm debug listening. Xdebug.show_exception_trace => Off => Off Xdebug.remote_log => no value => no value Xdebug.remote_host => localhost => localhost Xdebug.profiler_output_name => cachegrind.out.%p => cachegrind.out.%p Xdebug.profiler_output_dir => /tmp => /tmp Xdebug.profiler_enable_trigger => Off => Off Xdebug.file_link_format => no value => no value I believe that the xdebug is configured properly: I've also tried to set a breakpoint in PHPStorm and run the program on the AWS host, but the breakpoint isn't triggering. I've started to run the CLI program on the EC2 host, but a PHP error isn't causing PHPStorm to do anything. In the debugger window I have "Waiting for connections from Jetbrains IDE Support Extension for Chrome), but this is a command-line program, so Chrome isn't involved. I've clicked the "Listen" icon in PHPStorm.
xdebug.remoteport 'This must be the same port number as specified in the php.ini file: Xdebug 3.
#Phpstorm debug remote php code
Register the IDE, add Breakpoint in the code on the remote server.I have ssh setup to remote forward port 9000 on the AWS EC2 instance back to the host that has PHPStorm running on it. Debug port: in this field, specify the port for PhpStorm and the Xdebug engine to communicate through. Activate remote listening using the phone icon. NOTE: Do Not select the debuggin options on the browser when trying to debug the remote server.ġ6. Add Frontend and Backend server sto the XDebug settings on your Chrome browserġ5. When a CURL call is made to the remote server, modify the call to include this paramter in the URL:ġ4. Setup Debug Configuration and Directory Mappings for your project in PHP Stormġ3. A successful message is shown on the screen.ġ2. Click on the icon that looks like a phone to start listening to incoming traffic on port 9001.ĩ. Settings > PHP > Debug > XDebug > Debug Port – Set to 9001Ĩ. Modify the client port on the PHP Storm IDE. The above line translates to redirecting all traffic from port 9001 to port 9000.ħ. Create a batch file with the following lines of code to execute the python proxy server:Ĭd /usr/local/src/Komodo-PythonRemoteDebugging-7.1.2-73175-linux-x86/binĩ001 is the client port and 9000 is the local port. Zend_extension="/opt/xdebug/xdebug-2.1.4/modules/xdebug.so"ĥ. Modify the php.ini file under /etc/php5/apache2 and add the following lines:
#Phpstorm debug remote php install
Install xdebug on the remote server (xdebug.so)Ĥ. Use Komodo Python Remote Debugging Client – ģ. Install Python Library for Proxy setup on the remote server. Now – the proxy intermediates between your requests and the response from the server and thereby you are able to set breakpoints and debug code executing on the backend server.Ģ. Link the proxy server to the local debugger and the client on your desktop. Solution: Create a proxy server on the remote server. In such situations – the PHP Storm Debugger or the Browser may not be able to get debug information for the remote server. Or you may be making a CURL request to a remote server. Many occasions you’ll encounter that the frontend resides on a different server than where the backend code is.
0 kommentar(er)
