Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

drowl-init-from-existing: Inititate project using the copied projects "settings.php" #129

Open
joshsedl opened this issue May 4, 2023 · 2 comments
Labels
bug Something isn't working

Comments

@joshsedl
Copy link
Collaborator

joshsedl commented May 4, 2023

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

@joshsedl joshsedl added bug Something isn't working priority-high Issue with high priority labels May 4, 2023
@JPustkuchen
Copy link
Member

Rarely used, so maybe hiher priority than other issues, but not really high priority in total.

@joshsedl
Copy link
Collaborator Author

joshsedl commented May 4, 2023

Yea, maybe disabling it entirely, could be a bit too much, but yea

@JPustkuchen JPustkuchen removed the priority-high Issue with high priority label Oct 31, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants