Randy Fay

Great advice. Unless it's boiled down to something that demonstrates nothing but what PhpStorm does, it is unlikely to success. I was also confused by why you posted this in...

The problem with it starting an additional container at all is that it will ignore any DDEV configuration, so for example, the node version may not be right if it's...

Well, there are lots of other things that could be different :) It's certainly possible to use other ways to run node.

My suggestion of `ddev config --auto` was based on the assumption that the code is already laid down; it works well in that situation. DDEV detects docroot and subversion of...

If the code isn't there yet, then using `ddev config` to add hints of what's going on is a great technique, as in the quickstarts, which do the config before...

Related: will be automatically replaced with hyphen in next DDEV release, but of course you can do the same manually right now in the .ddev/config.yaml. * https://github.com/ddev/ddev/pull/6210 * https://github.com/ddev/ddev/issues/6206

In DDEV v1.23.4, projects automatically are named with underscores replaced with hyphens. Maybe a PR can add `ddev_version_constraint: '>=v1.23.4'` as a solution to this and not have to do anything...

`ddev.com` is already getting all the sponsors into `cache/sponsors.json`

This is marvelously easy to solve by just adding content to the existing remote-config. It just means the data has to be massaged into the upstream content, and added to...

@stasadev the last item here is putting the banner on the docs. I imagine we can do that with the upstream component, or ... - Would you take a quick...