Just started using DevKinsta and discovered this huge blocker to developer UX and productivity.
Has there been any progress with this?
Fwiw I’ve debugged with XDebug using Docker with Devilbox and 10up’s Docker WordPress installs, so it’s definitely possible if you can easily configure the necessary ini files and have the right info for the .vscode launch.json
One key setup variable I’ve found here is the XDebug remote host IP address, which should use the Ethernet IP Address not Virtual Switch (at least it was last time I did it with Devilbox). If you don’t get this right, no connection.
Ditto for the .vscode file/folder path.
But without official XDebug support, accurate setup information/instructions I’m wary of running down a rabbit hole trying to get this working at the moment - especially when I’m trying to solve client issues. Clients we are bringing to Kinsta btw!
Can you please prioritise this?
Interactive debugging locally is essential, logging is not a substitute when trying to solve gnarly issues -especially when you are on the clients budget time.
What’s also a productivity killer is I can’t even clone the site locally to Devilbox or 10UP Docker WordPress for debugging because even the DevKinsta tool won’t let me use All-In-One-migration or Duplicator to make an easy clone.
@michael While full support for interactive debugging enabled via the UI is the ultimate goal, I would very much settle for accurate set up instructions for DevKinsta and Visual Studio Code running on MacOS! Please could this be bumped up in priority because I resonate with @sonicviz’s sentiment regarding the necessity of local debugging – I have been stuck in this rabbit hole for months now!
There might be minor differences between 2 and 3 in the matter of config.
If you are using PHPStorm you can easily test your XDebug config, and you can add an XDebug log on the server too, to figure out what is causing issues.
By all means, if you do have the functional solution that fits your needs, it’s great.
I just wanted to share as there were questions about how to get it to work.
I think I was missing xdebug.idekey = VSCODE as I don’t VSCode, but PHPStorm.
due to some performance issues with docker (might be M1 related only) I commented out the log file.
It was impacting performance a lot. So after you get it working, you might want to comment it out.
I just wanted to add my voice to the chorus of “any ETA on this?”, as it cannot be overstated how critical xdebug is for any kind of local development environment for a PHP project. Some would say it’s pretty much the entire point of having a local sandbox.
Even if you can’t get a fully integrated Just Push A Button solution going soon, detailed instructions in the KB for PHPStorm and VSCode would go a long way to easing the pain and time.
To anyone else using PHPStorm, the only thing I had to do beyond the excellent community advise in this thread was to add path mappings in Settings → PHP → Servers for both servers (80 and 443), mapping /www/kinsta/public/SITENAME to C:\Users\MYNAME\DevKinsta\public\SITENAME.
Yes, I noticed this yesterday.
This problem came up with last update. I was on call with another expert @Codeable where we were trying to debug a problem, and noticed that mapping is now necessary for this to work properly.
Thank you for pointing this out, as I had idea to update my post, but forgot.