Stanislav Zhuk

This is a good thing to go in: - https://github.com/ddev/ddev/pull/6353#issuecomment-2210811014 Even if we decide not to add the same script for other add-ons in the future, this is the most...

Sure, but first I need to finish the parent task and it should probably be ready next week.

@graham73may, The error comes from `install.yaml`: https://github.com/ddev/ddev-browsersync/blob/4b8238c2d77d2596b4dd424d6991be8984e7dc8f/install.yaml#L45-L61

> I guess we'll have 3.4.4 in a bit today, if you don't mind re-running this. New images are pushed.

Working on this in: - #42

@n8-dev, We check for any `index.*` file in the `docroot`. If the warning is annoying, you can create a dummy `index.whatever` file in the `docroot`, commit it or add it...

Ideally, I would like to be able to change the default error message: - https://github.com/nginx/nginx/blob/5b8a5c08ce28639e788734b2528faad70baa113c/src/http/ngx_http_special_response.c#L124-L129 - https://github.com/apache/httpd/blob/628012369297dfaa27fe3cdbca51b6210433c821/modules/http/http_protocol.c#L1012-L1013 Why did they hardcode it? 🤔 Doing this requires patching the source code...

This PR should meet your expectations: - #7349 It’s simpler than adding a new config.

@n8-dev, If the `.htaccess` file matches this https://github.com/silverstripeltd/demo-project/blob/master/.htaccess Then using: ``` ddev config --docroot=public && ddev restart ``` would remove the warning, and the `docroot` change only applies to DDEV....

I see, so using `public` locally with DDEV does make a difference? Or is DDEV running directly in Silverstripe Cloud? (I might be missing the use case.) I used this...