Open jaakkolehtonen opened 1 year ago
Im using VSCode for step debugging with following config and everything works great:
.vscode/launch.json
{
"version": "0.2.0",
"configurations": [
{
"name": "Listen for Xdebug",
"type": "php",
"request": "launch",
"port": 9003,
"pathMappings": {
"/data/wordpress/htdocs/": "${workspaceRoot}/htdocs/"
}
}
]
}
.vscode/settings.json
{
"php.debug.ideKey": "vagrant"
}
Hi, this should be fixed in seravo/wordpress:nightly
. We're still testing and ironing out some stuff before we're comfortable releasing a new version for the development
tag. But if you could give the nightly version a spin and test that everything works nicely on your end too, that would be appreciated.
Hi,
seravo/wordpress:development
docker image ships with xdebug v3 but configuration (/etc/php/7.4/fpm/conf.d/20-xdebug.ini
) is still for v2.This fixes remote step debugging in v3: