#PHP SCRIPT DEBUGGER HOW TO#
#PHP SCRIPT DEBUGGER INSTALL#
#PHP SCRIPT DEBUGGER FULL#

next to the Servers field to create a new server.Ĭreate a Server Configuration for the PHP Docker container, configure Xdebug as the debugger and the path mapping that fits the folder structure within the PHP container It’s only important that you remember this key because we will use it later for the request to trigger the debugging.Ĭlick on the three dots. I usually choose something like IDEA_DEBUG. To be able to select this configuration, you may need to scroll down in the type selection popup (“Add New Configuration”) and click on “52 items more (irrelevant)” in order to find the type “PHP Remote Debug”.Ĭreate a Debug Configuration in IntelliJ IDEA Ultimate/PhpStorm of the type ‘PHP Remote Debug’ which connects to our PHP Docker container via XdebugĮnter an arbitrary key for Ide key(session id).

src:/var/www/html/ ports : - '80:80' Configure IntelliJ IDEA Ultimate or PhpStormĬreate a Run Configuration of the type “PHP Remote Debug”. Version : '2' services : apache_with_php : build. Afterward, we have to configure Xdebug with some properties in the php.ini.

#PHP SCRIPT DEBUGGER INSTALL#

Within the Dockerfile we install and enable Xdebug using pecl and docker-php-ext-enable. Therefore, we create an own Docker image based on the PHP/Apache image. Xdebug runs within the PHP container and connects to the Xdebug server controlled by IntelliJ IDEA Ultimate/PhpStorm Install and Configure Xdebug in the PHP Docker Containerįirst of all, we need to install and activate Xdebug in our PHP container.

#PHP SCRIPT DEBUGGER HOW TO#

But how can we debug the PHP code running in the container? In this post, I show you how to configure Xdebug in a PHP container and configure IntelliJ IDEA Ultimate or PhpStorm for remote debugging. Running PHP and an Apache in a Docker container is very handy for local development. Configure IntelliJ IDEA Ultimate or PhpStorm.Install and Configure Xdebug in the PHP Docker Container.For security purposes, we don’t want to show the error message, and script name to the user.Java Ecosystem, Kotlin, Engineering Management, Sociology of Software Development Debugging within a PHP Docker Container using IDEA/PhpStorm and Xdebug On a live server, we hide the error messages but keep them in a log file. Yep, these should be hard-coded into php.ini already. ini_set('error_log', 'PATH/error.log').When you are working on your test server, just set PHP to show all errors. But if we turn off error_reporting(), no errors will be reported at all. That is, we can turn off display_errors but still keep the errors in a log file.

display_errors simply sets if the error should be displayed on the screen.

Error reporting sets what kinds of errors need to be reported.

Don’t confuse this with error_reporting().

display_errors display the error on the screen.

log_errors specifies if you want to save the errors into a log file.

#PHP SCRIPT DEBUGGER FULL#

Will leave a link below to the full list. PHP has a long list of error levels, from important E_WARNING to “notice only” E_NOTICE.

error_reporting() – Set the error reporting level.

When it comes to error reporting in PHP, there are only 3 mechanics: Ini_set('log_errors', 1) // SAVE ERROR TO LOG FILE error_reporting(0) // NO ERROR REPORTING error_reporting(E_ALL) // ALL KINDS OF ERROR E_ALL, E_WARNING, E_STRICT, E_PARSE, E_DEPRECATED, E_NOTICEĮrror_reporting(E_ALL & ~E_NOTICE) // ALL EXCEPT NOTICES

Php script debugger