-
-
Notifications
You must be signed in to change notification settings - Fork 579
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
DDEV could manage Docker providers and offer hosting providers #6215
Comments
One suggestion per issue is better :) My first impression is that we could not successfully manage all the Docker providers in the world. Docker Desktop does not even have a command-line interface. And on WSL2 Docker Desktop users don't have access to the Windows side; For docker-ce sudo would be required. I don't think the majority of users use the hosting providers, and we aren't even aware of most of the ones people use outside the Drupal ecosystem, except Platform.sh |
One of the worst things historically about Lando is its attempt to manage Docker Desktop. By default, from years back, it has depended on an explicit (and usually outdated) version of Docker Desktop, and has installed that version by default during its install process. Having experienced that in the earliest days we always committed to avoiding that kind of thing. |
It's true we don't know what people use outside of the Drupal ecosystem use, it be great to hear from them. Same way we create a settings.ddev.php automatically we could make a .env file based on the items require by a hosting providers. We already have the ability for them to put variables on their .env or config.yml but a wrapper that does it for you after you enter a key/token would be interesting for early adoption. In regards to manage docker providers. I can see how that be a challenge. I will look into it a bit more. If DDEV is aware that it ran inside colima or docker desktop maybe it can prompt back what the command is for the last environment it ran into. Save the environments on some sort of log. So instead of just Could not connect to a docker provider maybe it can give hints to which ones it has connected before and the command to start them. Start small and move on from there. |
Thanks for listening to people!
I'd be interested in more explicit feedback about people's challenges. People use such a huge variety of hosting providers that I don't know how to handle that well. Also note that DDEV's goal is to be a local development environment, so that's always going to be our focus. |
That makes sense, i will look into it some more. The idea is to use what we already and wrap it from a different angle. Get the 80% gains with 20% of the effort. Local first but once you are ready hit
I use those two since I'm most familiar with them but the idea is if some need an extra variable it be on more step but that be it and then ddev pull be linked. Behind the scenes the env file will be populated on that given project. Ps: I just noticed there used to be a The wrapper might just be a command that redirect users to terminus or acli and then rely on the to keep their tool up to date and then we just have to save the token on the local env file. |
DDEV hasn't had |
Is there an existing issue for this?
Is your feature request related to a problem?
At DrupalCon Portland a few improvements were discussed.
ddev start
instead of just failing. If multiple environments are detected such as docker desktop and colima, the user could be prompted with an option to start either. If only one is present thenddev config
and have their setup simplified. Probably at the end of the current prompts, we could ask the user if they would like to set up a hosting provider and based on that create .env file and place their tokens in there.Describe your solution
see above
Describe alternatives
No response
Additional context
All of this with goal of increasing developer adoption as we ease their transition from other tools.
The text was updated successfully, but these errors were encountered: