Randy Fay

I would like it if `ddev describe` gave at least some information on a stopped project too. It's always disappointing to see the empty boxes.

What do you think about auto-starting ddev when `ddev describe` is done, like so many other things? I'd like that. It solves the problem of the fact that we use...

Would you consider doing a PR against https://github.com/ddev/ddev/blob/fec8d695ffd89634060ed10d465ce6ba6f0f87ff/pkg/ddevapp/backdrop.go#L164 ? You just click the pencil in the upper right:  Alternately, you could add a redirect on docs.backdropcms.org, but we're happy...

Looking forward to your PR, thanks.

Thanks for the thoughtfulness about creating these issues! We spent some sigificant time talking about this particular one, and about splitting webserver from php. The usability cost to users would...

Oh, that wouldn't be as hard, thanks. And if done like we do ddev-dbserver it would be done in parallel and pretty fast. It would mean changing PHP version would...

One conversation to have about these strategies: DDEV has always been focused on local development, and every alternate use (like CI or hosting) has always been considered just "gravy", extras...

We've long had one-off techniques for even older versions of PHP in ddev/ddev-contrib. We could stop providing 5.6 and 7.0 and 7.1 and instead have an add-on for those. With...

I'm really liking this initiative. My current thinking on options: 1. Keep the configuration as it currently is (driven by php_version), but remove all old versions up through 8.0. Then,...

> To start, let users manage this just by setting webimage directly. Avoid adding new config options for now. We'd need to fix the issue of ddev force-downloading ddev/webserver even...