Set transaction isolation level to 'READ COMMITTED' in DDEV config

pameeela → credited dunx → .

Hmm. DDEV docs say this should be done by default: https://ddev.readthedocs.io/en/stable/users/usage/cms-settings/#database...

I think this must be new-ish because I don't remember seeing it before, and it's not included in 📌 Audit warning messages shown in the status report after installation Active . Perplexing.

That is weird. I think probably we should run this past @rfay.

Yeah, chatting in Slack. Seems to be something funny about ddev rebuild, it goes away if I run ddev restart.

So that deletes all of the docroot, which means the settings.ddev.php is gone until you do a ddev restart after laying down the code again

@dunx not sure if you're following this issue but wondering how you installed? If you were using the zip file, you shouldn't see this warning.

I'm also seeing the warning on a new install from the repo using ddev start.

phenaproxima → credited rfay → .

Crediting @rfay for some input in Slack.

Confirmed this works as expected.

Merged into 1.x and cherry-picked to 1.0.x. Thanks!

I was using the zip file @pameeela. I'lll re-test all of these Status Report Warning issues today using the latest 1.x. I'll have a play around with ddev rebuild and ddev restart and report back.

ddev rebuild is not part of the zip file and never will be. It’s only for internal development. So no need to pay any further attention to this. :)

I performed a latest install from git:

git clone https://git.drupalcode.org/project/drupal_cms.git
cd drupal_cms
ddev config --project-type=drupal11 --docroot=web --php-version=8.3
ddev start
ddev composer install 
ddev launch

Now admittedly, it did take a few attempts to get what I wanted, but the final build was preceded by a:
ddev stop --omit-snapshot --remove-data
which I think should have resulted in a clean install.

On completing the installation and visiting the Status Report page, I still see the "Transaction isolation level" warning.

You do have to do a `ddev restart` one time. After doing that and moving on with the `ddev rebuild` command I expect you won't see the warning. The command to set up the database happens on start (post start) with a Drupal project.

I can confirm that if you perform a ddev restart on your container then this status warning goes away.

I came to this issue because I was seeing the warning after running the launch-drupal-cms.sh script that "we" had provided for people to "Try it out locally" at https://new.drupal.org/drupal-cms/release-candidate.

I'm not sure how we'll be asking people to install Drupal CMS 1.0, but if we can add a ddev restart to any script provided that would be good. Does anybody know here whether the same script-based launcher will be used or something else, so I can raise this as a separate issue for that script?

Automatically closed - issue fixed for 2 weeks with no activity.