fix: when settings files not set, don't chmod, fixes #5675 #5676
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The Issue
php
shouldn't try to create settings files, should it? #5675Projects with no settings may fail when starting outside homedir. They shouldn't even be chmodding in that case
How This PR Solves The Issue
Manual Testing Instructions
Run
ddev start <somephpproject>
in the root directory of a linux machine. It should work fine.Run
ddev start <somedrupalproject>
in the root directory on linux, it should work and unwriteable settings files should be chmodded properly.Automated Testing Overview
Related Issue Link(s)
Release/Deployment Notes