![]() Used together, these tools will allow you to debug your code in an environment that is as close to production as possible without adding the burdens and risks involved with your debugging tools. My recommendation is to check out VirtualBox, Vagrant, and SaltStack. The important thing in the Xdebug settings is that you use the actual IP of the host computer in xdebug.clienthost instead of 127.0.0.1. Spend some time learning about Virtual Machines. And don't run debuggers on your production gear. These are the php.ini settings, other than the driver path, that I am using for my CLI project: xdebug.remote_enable = 1 Make sure that you can get XDebug working without PHPStorm, then circle back around and integrate it. Have you set the preferences correctly in your project? Were you able to configure and validate your deployment server (under Deployment)?Īfter that, set up the server under PHP > Server and validate it as well.ĭon't forget to check the firewall on your host. I would have added this to the comments, but don't have the needed rep. Break at first line: yes Servers: Name: 'Debian' Host: 192.168.56. If someone could help me figure out what I'm missing or doing wrong that would be great! I also followed this different tutorial but in the Integrating XDebug with PhpStorm step I don't have the choose XDebug from the Debugger drop-down list option on step 3 I followed this Zero Configuration tutorial, but at step 7 I never get the Incoming Connection dialog. I've also tried 2 different approaches to set all this up: Also, I'm not setting the remote_host IP because I'm using the remote_connect_back option to allow multiple IPs, as explained here. I'm not setting the remote_port variable because I'm fine with the default port (9000). ![]() Xdebug.profiler_output_dir='/home/username/debug' This is how the config in php.ini looks like: zend_extension="/usr/local/src/xdebug-2.1.0/modules/xdebug.so" If you've never had to set it up yourself. To test that I've done whats recommended in this other SO question, and all those things work. Debugging for WordPress using Xdebug in PhpStorm is a great way to track down hard-to-find bugs. I have installed Xdebug 2.1.3 on the production server, and it seems to be working. Now I would like to start using Xdebug to debug the websites using the production server (PHP 5.3.28), so I'm trying to set up remote debugging with phpStorm and Xdebug. So far all pretty simple, no issues at all. I have a copy of the website on my computer, make whatever changes there and upload the new version to the production server via the integrated FTP tool. I'm using phpStorm 8 to develop PHP websites (CakePHP 2.5.1 in this specific case). I've seen other questions/answer about this topic but none of them seem to have the same issue I have, so here we go:
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |