Nico Löber

As already mentioned, the ID should not be changed, so I will close this issue.

Scheduled as an optimization for v1.1 as setting it has no negative impact, so it's not urgent.

> What I can say is that in my setup, when I delete the envionment variable manually, phpstorm is unable to connect to the docker-compose service. I can confirm that....

Removing the `COMPOSE_PROJECT_NAME` environment variable still results in the following error, @rfay:  Testet with ddev 1.22.5 and the main branch of the plugin.

Very interesting finding @AkibaAT! But could someone explain again why setting the environment variable is a problem? I didn't notice any issues...

Hey, I will review it soon. I was in Greece the last few days. There are a few more people with permissions, if anyone is interested to support me, please...

Sadly updating the plugin is not just to increase the versions. You always have to check for deprecated API uses and changed behavior. Sadly it is quite hard to work...

@Aneida please mail me at [email protected], so we can exchange contact information, thanks!

To keep you updated: Current problem is a change in behavior of the IntelliJ Platform. All calls to cli binaries that happen in the background (used for ddev and docker...

Todo list to for 2024.1 compatibility: * [ ] https://github.com/php-perfect/ddev-intellij-plugin/issues/311 * [ ] https://github.com/php-perfect/ddev-intellij-plugin/issues/312 (Lowest priority as it is not critical) * [ ] https://github.com/php-perfect/ddev-intellij-plugin/issues/313 Sadly I will be unavailable...