To efficiently debug you must change max execution time both for PHP and your server. You can find these setting in the following menu: Then add server configuration and mapping in PHPStorm settings, like you always do. To be able to debug your Drupal project, you must have your project locally and on the remote server. Please note that 9000 port destination is Remote, so make sure you select the correct radio button while adding port mapping. 3306 is for MySQL and 9000 is for Xdebug. Just add a new tunnel to your existing connection and you are good to go.Īs you can see, I'm using two forwarded ports. If you are using Windows then Putty is the best tool. You need to set up a SSH tunnel between your local machine and the remote server. When you start to debug just click on the extension's icon and click on the Debug button.
Phpstorm remote development install#
To make debugging easier you need to install Xdebug helper extension for Chrome web browser. Now you can restart PHP by executing: systemctl restart php7.0-fpm SSH to your server and open this file: vim /etc/php/7.0/fpm/php.iniĪnd add the following lines at the end of the file: Look for Loaded Configuration File value, and that is where you php.ini is located. You can do that by visiting the following page in your Drupal instance: Now you need to locate your php.ini file. To install Xdebug execute the following command: sudo apt-get install php-xdebug
Phpstorm remote development how to#
I will show you how to install Xdebug on Ubuntu 16.04 and PHP 7. You can of course apply the same technique to some other PHP framework or CMS.įirst step is to install Xdebug PHP extension. In this blog post I will show you, how you can easily set up remote debugging for Drupal projects. So, to be able to really follow the execution of your code and state of variables, you need to use a proper debugger. This can be a very time consuming process. You have to call these functions from your code and then inspect what will they print out on your screen. Old school method for debugging is good enough if you are debugging something simple, but when it comes to the more complex parts of your code, using var_dump or Devel is not good enough. You will reach a point when you need to see what is happening in your code. If you are working on some project that is not trivial and simple, then you know that it's not always a smooth sail. And when it comes to debugging Xdebug is certainly the best tool. To be a really efficient developer, you have to use the best tools available.
0 kommentar(er)
