Jump to content

Using DDEV for local ProcessWire development (tips & tricks)


bernhard

Recommended Posts

10 hours ago, nurkka said:

does anybody use PHPStorm within WSL2 and could share some insights

I use it with great speed (not using Mutagen, as it is not needed in WSL2). I also work with VScode (with WSL plugin from Microsoft) and it also works great.

  • Thanks 1
Link to comment
Share on other sites

7 hours ago, cst989 said:

One thing I've found is that most environments will show php warnings when using

$config->debug = true

but ddev will not. Does anyone worry/do anything about this?

This hasn't been my experience. DDEV shows both warnings and fatal errors. I haven't had to do anything special. What's your environment?

  • Like 1
Link to comment
Share on other sites

  • 4 weeks later...
On 11/6/2024 at 9:41 PM, kongondo said:

Anyone got xdebug + WSL2 + DDEV + VScode working please? I have read the tut in the DDEV docs but it is not working for me.

  1. In VSCode the Xdebug session starts. On the website Xdebug doesn't kick in. 
  2. After a while, VSCode breakpoints turn transparent and hovering over them says 'invalid breakpoint' or something like that.
  3. I did attempt all the WSL-related troubleshooting in the DDEV docs, e.g. the telnet connection. Was hoping for a question here.
  4. After a while VSCode says port 9003 closed.
  5. Sometimes I see notifications from ProcessWire (e.g. headers already sent) in the debug output.
  6. I am not sure whether and how to append the port number 9003 to the ddev url. E.g. mysite.ddev.site:9003. If I do this, the website hangs (chrome website cannot be reached).

Any ideas?

Thanks!

Good day, @kongondo! Have you managed to get it to work?

Link to comment
Share on other sites

  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...