Randy Fay

Thanks for maintaining this! There is in fact expectation of auto-start that we see doing support, but I think it's important to keep the default what you like it to...

I think your approach is fine, and thanks for explaining how to do the auto-start in #60

@deviantintegral we already do separate names for multi-level domain names. They're just not wildcards. So we already can do one.two.three.four.ddev.site. We just can't do it with a wildcard.

Please add a little more detail, including specific examples, of what you envision, thanks.

Thanks, please update the OP to show what the current problems are and how they should be improved.

It may or may not work out that way. It depends on both the docker provider and whether the container is run as a different user that root. But we've...

Note that the `working_dir` in the other issue was *not* in the .ddev folder, and it's not terribly common for things to be created inside a container and show up...

I guess the proposal here is pretty modest: Just warn if something in the .ddev directory (or perhaps in the whole project?) is not owned by the user.

I think you're using an old version of DDEV maybe? You did a `ddev debug test` originally that showed expired certificates? What does `ddev --version` say?

Yes, the nginx project let their cert expire. You have two versions of DDEV installed, `which -a ddev` will show them to you. I think this will help you sort...