kongondo

In case you need it, DDEV Manager for VS Code.

The integration of WSL2 and file explorer is very seamless. One can copy files between them as if they were on the same system. Even terminal integration is seamless. I never used WSL 1 so I don't know if it has always been like this.

I'd say give it a try. It's literally 2 steps. I did this recently. I didn't do step #3 there. Certs, multi-sites, etc., all work.

Anyone got xdebug + WSL2 + DDEV + VScode working please? I have read the tut in the DDEV docs but it is not working for me. In VSCode the Xdebug session starts. On the website Xdebug doesn't kick in. After a while, VSCode breakpoints turn transparent and hovering over them says 'invalid breakpoint' or something like that. I did attempt all the WSL-related troubleshooting in the DDEV docs, e.g. the telnet connection. Was hoping for a question here. After a while VSCode says port 9003 closed. Sometimes I see notifications from ProcessWire (e.g. headers already sent) in the debug output. 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!

For anyone reading this, I have been working with @Spinbox to implement a webhook solution + other backup (of session) solution. It is currently being (user) tested and has been implemented as Padloper 011. Will keep you posted!

I have recently had the same experience. In my case it looked like the culprit was DevSense PHP Tools. I gave up on it but the problem persisted with PHP Intelephense. Finally I gave up and went back to local development and set up a CICD with GitHub Actions which watches my main branch and pushes stuff to the server when main branch is updated. Works a treat!

Hello. Thanks for your work and report. Welcome to the forums.

What version of DDEV are you using? I know there is a recent update, 1.23.5. I am wondering whether this could be responsible for the slowness? I am on version 1.23.4 and have not upgraded yet (and running in WSL2 as mentioned earlier).

I see, thanks. In my case, the consideration is mainly if it can run an LLM locally without 'much fuss'.

M4 Pro beyond your budget or you have no need for the beast?

Dude! Now you've got me really, I mean really, interested! Aside from the 'marketing' talk (in the announcement), this little guy looks like it packs a powerful punch! All that and managing to keep it cool? Hmm. We are seriously OT-ing, sorry, but are you able to please recommend a 'portable' screen to go with it? Thanks!

Actually you don't. Make sure you are not connected to the internet and it will ask you if it can create one at a later time or skip or something like that 😁. Hmm, sounds very strange! 6 hours! Even with a slow internet connection this still seems very odd. I use a debloated Windows but that alone cannot explain why I haven't experienced such a long install time as you did. Granted, you had to install other stuff as well.

No, I haven't. I tried a Mac once and the app window buttons location on the left (instead of the right) just confused me 😃. Thanks for the suggestion thoug.

And this is good time to say thanks to @bernhardand others here for making me look at DDEV! For some reason I used to confuse it with Devil Box. DDEV is great! I have it working for different sites some of which are in a multi-site setup with different databases but one ProcessWire.

Works fine for me. What 'didn't work'?