-
-
Notifications
You must be signed in to change notification settings - Fork 10
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
Add-on shouldn't use jq, base64, perl, etc without some notice or requirement #46
Comments
Hi @rfay So, if i recap :
so, as a suggestion, maybe next steps for this addons should/could be :
My 2 cents ps: you can close the issue :P |
ok,
So i guess it is the step where you try to find in the environment variable, all info about DATABASE_* ? |
It's probably because you don't have |
you're right, now it's fine :
|
However, I didn't know that DDEV required |
homebrew |
Could you please report an issue about this on DDEV Homebrew tap? |
I didn't think there was anything in the current release of this add-on that required jq, but there is. There's nothing about ddev that requires jq, it's just that this add-on uses it one place. That's a mistake. So no need to fiddle with homebrew tap |
This is important to solve, both because we don't want to depend on user configuration, but also because |
Hi @rfay
i can't get my Symfony project to be configured using ddev addon.
This is what i get from the command line :
Let me know if you need me to grant you access to this project, it's the SFCon workshop that we will handle with Sylvain.
note: ddev start is just a fail try, to be sure that ddev can't start as it is.
The text was updated successfully, but these errors were encountered: