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
There are several issues, with the drowl-init-from-existing command. One of the biggest issues is, that it currently doesn't use the remote projects "settings.php". This leads to several issues, e.g. #67.
As long as we do not let the user provide the "settings.php" and initiate the project, based on its values, I will disable the command, as it is very unreliable.
There are several issues, with the drowl-init-from-existing command. One of the biggest issues is, that it currently doesn't use the remote projects "settings.php". This leads to several issues, e.g. #67.
As long as we do not let the user provide the "settings.php" and initiate the project, based on its values, I will disable the command, as it is very unreliable.
When trying to fix this problem, we should also, work on other "dife" issues, see:
https://github.com/webksde/ddev-vscode-devcontainer-drupal-template/issues?q=is%3Aissue+is%3Aopen+drowl-init-from-existing
The text was updated successfully, but these errors were encountered: