Closed timkelty closed 3 months ago
In my understanding the --service
refers to a container which is part of a docker-compose project. docker-compose uses the word "service" for that. "mailpit" is currently not a service in that sense but merely a program that runs in the "web" container.
"launch" opens an URL.
A service does not necessarily have a URL. DDEV could check if it published any ports via the router (by looking into the HTTP(S)_EXPOSE
env settings) and could theoretically launch the first one?
I think your wish is conceptually a bit difficult but I might overlook something.
Note: We have now a command ddev mailpit
as alias for ddev launch -m
(#5642)
I'm working on PR #5525 that will allow you to use ddev port 3000
to open a specific port.
This will make custom commands and alias much easier to develop.
Thanks for the clarification – in my case (ignoring my mailpit example), I am trying to launch URL from a docker-compose service (defined by HTTP(S)_EXPOSE
).
Sounds like this is by design, so for now I'll just do this by defining a separate custom command.
ddev launch
has in fact been updated to take ports, for example, so ddev launch :8037
, which gets you part of the way there.
Is there an existing issue for this?
Is your feature request related to a problem?
Services often have their own web UIs, which are shown via
ddev describe
, but not available toddev launch
Describe your solution
Like
ddev exec
, it would be nice if one could do:Describe alternatives
No response
Additional context
No response