Setting up a debugger in Nusphere PhpEd for remote debugging of web services
Nusphere PhpEd has a debugger for php scripts that allows you to debug and profile web services of any complexity and with any structure on a remote server. The only requirements for its normal operation is an open port on the computer from which debugging occurs, and the connection of the debugger module that comes with PhpEd to php.
After the release of Weborama 2.0, we finally made a feature-freeze and it was time to seriously do refactoring. For this, it would be nice to use a debugger. Personally, I really envy those who use the debugger to work on an ongoing basis. We failed to implement it from the very beginning and somehow abandoned this business. But now, in view of the complexity of the relationship between the various modules of the project, we began to lose a lot of time using the “classic” debugging methods (var_dump, print).
')
That's how I remembered the debugger built into PhpEd again. But since our production is located in different places, we go to the development server remotely. Therefore, we had to raise it according to the most difficult scenario, which is described below:
Next comes the text of our technologist (with my edits to make it more or less abstract), who wrote the article in the corporate wiki (If successful, the author will not get an invite for Habr, since he already has an account andrushkaaaa :)):
Using the example of PhpEd 5.6 and hypothesing dev.weborama.ru (all folders and projects can be called as you please, in order to avoid paranoia I do not write every time that “this folder can be placed anywhere” or “here you can choose any name”)
1. First, let's do the server. Copy the desired debugger version to the server from the PhpEd installation / debugger subfolder.
2. open the php.ini file and list the following in it:
3. restart the web server, fast-cgi daemon, backend or whatever you have.
4. Now the client. At C: \ Documents and Settings \ {computer name} \ Application ata \ NuSphere \ PhpED \ create a folder myWorkspace
5. Inside the myWorkspace create the projects folder, inside it the dev.weborama.ru folder where the project files will be stored.
6. Download or put there the whole project.
7. Open PhpEd
8. In PhpEd choose New project.
9. Switch to Wizard mode if it did not happen automatically.
10. Select "Web server is on a remote machine."
11. Specify the project root as C: \ Documents and Settings \ {computer name} \ Application Data \ NuSphere \ PhpED \ myWorkspace \ dev.weborama.ru
12. Click the Accounts button.
13. Configure FTP account for dev.weborama.ru
14. Choose it as Publishing account .
This will allow you to synchronize your local code with what is on the server.
15. In the next step, download the dbg-wizard.php at the specified link and put it in the root of the project on FTP yourself. Relieve your headache. Then provide a link to it.
Next, click "Next" until you reach the finish line. I can not go with you, because the project is hypothetical. If there are problems, then write in the comments - we'll figure it out.
After all this, you can consider your project ready for debugging.
16. If you are behind a firewall, then make sure that port 7869 (by default) sticks out and accepts connections. Also, if you want more security and you have a static IP, then prepare it, we will need it in the settings for the server part of the debugger.
17. now open any project php-file in phpEd and press F9 or Run in debugger in the debug panel. If everything is done correctly, then you will start a debugging session.
Thanks for attention.
PS : If you're interested, next time I will write how to make friends with PhpEd project with Subversion and set up a debugger for several developers.
After the release of Weborama 2.0, we finally made a feature-freeze and it was time to seriously do refactoring. For this, it would be nice to use a debugger. Personally, I really envy those who use the debugger to work on an ongoing basis. We failed to implement it from the very beginning and somehow abandoned this business. But now, in view of the complexity of the relationship between the various modules of the project, we began to lose a lot of time using the “classic” debugging methods (var_dump, print).
')
That's how I remembered the debugger built into PhpEd again. But since our production is located in different places, we go to the development server remotely. Therefore, we had to raise it according to the most difficult scenario, which is described below:
Next comes the text of our technologist (with my edits to make it more or less abstract), who wrote the article in the corporate wiki (If successful, the author will not get an invite for Habr, since he already has an account andrushkaaaa :)):
Using the example of PhpEd 5.6 and hypothesing dev.weborama.ru (all folders and projects can be called as you please, in order to avoid paranoia I do not write every time that “this folder can be placed anywhere” or “here you can choose any name”)
1. First, let's do the server. Copy the desired debugger version to the server from the PhpEd installation / debugger subfolder.
2. open the php.ini file and list the following in it:
zend_extension = /path/to/debbugger_extension/dbg-php-5.2.so [debugger] debugger.enabled = on debugger.profiler_enabled = on # if you want to use the profiler debugger.hosts_allow = your IP address debugger.hosts_deny = ALL debugger.ports = 7869 10000/16
3. restart the web server, fast-cgi daemon, backend or whatever you have.
4. Now the client. At C: \ Documents and Settings \ {computer name} \ Application ata \ NuSphere \ PhpED \ create a folder myWorkspace
5. Inside the myWorkspace create the projects folder, inside it the dev.weborama.ru folder where the project files will be stored.
6. Download or put there the whole project.
7. Open PhpEd
8. In PhpEd choose New project.
9. Switch to Wizard mode if it did not happen automatically.
10. Select "Web server is on a remote machine."
11. Specify the project root as C: \ Documents and Settings \ {computer name} \ Application Data \ NuSphere \ PhpED \ myWorkspace \ dev.weborama.ru
12. Click the Accounts button.
13. Configure FTP account for dev.weborama.ru
14. Choose it as Publishing account .
This will allow you to synchronize your local code with what is on the server.
15. In the next step, download the dbg-wizard.php at the specified link and put it in the root of the project on FTP yourself. Relieve your headache. Then provide a link to it.
Next, click "Next" until you reach the finish line. I can not go with you, because the project is hypothetical. If there are problems, then write in the comments - we'll figure it out.
After all this, you can consider your project ready for debugging.
16. If you are behind a firewall, then make sure that port 7869 (by default) sticks out and accepts connections. Also, if you want more security and you have a static IP, then prepare it, we will need it in the settings for the server part of the debugger.
17. now open any project php-file in phpEd and press F9 or Run in debugger in the debug panel. If everything is done correctly, then you will start a debugging session.
Thanks for attention.
PS : If you're interested, next time I will write how to make friends with PhpEd project with Subversion and set up a debugger for several developers.
Source: https://habr.com/ru/post/59006/
All Articles