You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The IDE does already check if there is any update for ddev available.
I would expect a "update now" action in the notification about the new version and the missing ddev insallation notifications.
This should download and install the latest version of ddev.
The implementation should be quite easy for windows as the installer can be used.
For WSL using the Windows version would make things easy. Also this would reduce complexity, as currently the version information have to be collected on project level instead of application level, as you can have a ddev project in WSL and one in Windows with differing ddev versions at the same time. https://gist.github.com/nico-loeber/6d6e8261827c5e4efa4ccf5b5cd04140
For Mac and Linux systems there is a bash script to install ddev. It has to be checked if this can be used.
When installing ddev it should be in path even for non login shells if possible.
Login shells can cause serious performance problems if something like zsh with plugins is used.
See: #23
The text was updated successfully, but these errors were encountered:
The IDE does already check if there is any update for ddev available.
I would expect a "update now" action in the notification about the new version and the missing ddev insallation notifications.
This should download and install the latest version of ddev.
The implementation should be quite easy for windows as the installer can be used.
For WSL using the Windows version would make things easy. Also this would reduce complexity, as currently the version information have to be collected on project level instead of application level, as you can have a ddev project in WSL and one in Windows with differing ddev versions at the same time.
https://gist.github.com/nico-loeber/6d6e8261827c5e4efa4ccf5b5cd04140
For Mac and Linux systems there is a bash script to install ddev. It has to be checked if this can be used.
When installing ddev it should be in path even for non login shells if possible.
Login shells can cause serious performance problems if something like zsh with plugins is used.
See: #23
The text was updated successfully, but these errors were encountered: