The launcher script can cause an error if a DDEV project with the same name already exists

Hmmm...postponing because for some reason I can't reproduce the error condition. Maybe newer versions of DDEV are smarter?

This is what I reported earlier but I’m sure you know that…

You moved back to review… should I?

I manually tested this and even wrote automated test coverage which confirms that ddev config is invoked as intended.

Cool beans... here's what I did:

1. Installed rc2 in one place without MR code
2. Installed rc2 in another place without MR code and got error
3. Downloaded the installer script to "another place" and retried and it worked and named it drupal-cms-3

I assume 3 because I have a drupal-cms-dev project? Doesn't really matter but it's different and works :)

All good! Thanks for this... so nice.

macbookpro:drupal-cms kristenpol$ ./launch-drupal-cms.sh
Creating a new DDEV project config in the current directory (/Users/kristenpol/Sites/quant/cms/testing-ddev2/drupal-cms) 
Once completed, your configuration will be written to /Users/kristenpol/Sites/quant/cms/testing-ddev2/drupal-cms/.ddev/config.yaml
 
Configuring a 'drupal11' project named 'drupal-cms-3' with docroot 'web' at '/Users/kristenpol/Sites/quant/cms/testing-ddev2/drupal-cms/web'.
For full details use 'ddev describe'. 
Unable to set permissions inside container on settings files: '' 
No settings.php file exists, creating one 
Configuration complete. You may now run 'ddev start'. 
Starting drupal-cms-3... 
Building project images... 
...

Crediting @kristen pol for manual testing.

Merged into 1.x and cherry-picked to 1.0.x. Nice to have this little quality of life improvement. Second impressions matter!