Randy Fay

Another interim step would be to just do a quick start in the docs.

A great start!

Reasons for explicit CraftCMS support: * Explicitly craft custom commands like `ddev craft` * Explicit nginx config * Settings management

* The `ddev craft` command now shows for everybody who uses the `php` project type, which increases the complexity level and isn't necessary. * I don't know that craft will...

Ah yes, upload_dir. Added that to the list above. DDEV has no idea where upload_dir is by default in a craft project that's set to project type php. Added to...

How is the upload dir configured? In most CMSs, configuration like this is provided somewhere in code. Can the database configuration be provided in code, like Drupal does settings.php or...

So a Craft project type could create a .env file like is done for Laravel...

Could you please provide links to the docs about upload_dir and db config?

TYPO3 also can have more than one "uploads", and Drupal has both public and private, so DDEV's single dir is a long-term mistake :) Thanks for the help!

I don't think this strategy actually works; it seems you have to push a new tag. Will keep pushing new tags.