![phpstorm remote debug phpstorm remote debug](https://intellij-support.jetbrains.com/hc/article_attachments/360000030110/blobid0.png)
If you have the router cache enabled, you will also need to explicitly add the Xdebug cookie ( XDEBUG_SESSION) to the cookie whitelist.
Phpstorm remote debug full#
Consult the Xdebug documentation for a full list of available options, although in most cases the default configuration is sufficient.
![phpstorm remote debug phpstorm remote debug](https://wptavern.com/wp-content/uploads/2015/07/introduce_parameter.png)
They are all set as php.ini values, and can be configured the same way as any other php.ini setting. Xdebug has numerous other configuration options available. All other requests will be directed to the normal PHP-FPM process and thus have no performance impact. Only incoming requests that have an Xdebug cookie or query parameter set will be forwarded to the debug PHP-FPM process. When that key is defined, Platform.sh will start a second PHP-FPM process on the container that is identically configured but also has Xdebug enabled. The idekey value can be any arbitrary alphanumeric string, as long as it matches your IDE’s configuration. Instead, Platform.sh runs a second PHP-FPM process with Xdebug that is used only for debug requests, leaving the normal process unaffected.Įnable Xdebug by adding the following configuration to the application’s. Xdebug has a substantial impact on performance and should not be run in a production process. Xdebug is not enabled the same way as other extensions, as it should not be active on most requests. It is available on Platform.sh Grid instances running PHP 7.2 and higher.Īs configured on Platform.sh, it avoids any runtime overhead for non-debug requests, even in production, and only allows connections via SSH tunnels to avoid any security issues. While usually used for local development, it can also be helpful for debugging aberrant behavior on the server. Xdebug is a real-time debugger extension for PHP.