joshsedl
commented
1 year ago The attached issue fork already fixes part of the problem, for some reason, when testing the issue fork, running the "drowl-init" throws an error, that this command doesn't exist, even if it clearly exists in the current folder structure.
Additionally, the fork's implementation is not finished yet, we need to dynamically change the "ddev code" command's hexified project name to the initiated project name.
Currently, it is only possible to have one ddev-vscode project instance at once, since the project name and ddev code command is predefined and not dynamic, BUT there currently is now a "--auto" ddev config command flag, which enables initiating a ddev project without prompting the user for any configurations.