[Set-up] Readded ACL file permission docs #14327
Merged
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.
We dropped all this documentation because Symfony 4.0 came with a great improvement on this topic - using
umask
in dev environments.However, setting up file permissions is still required in non-dev environments when Symfony has to dynamically write to the
var
directory (e.g. logs or file-based cache, including doctrine query result cache). Currently, the docs say "One way this can be done is by usingchmod -R 777 var/log/
.", I would argue that this is the worst method to fix the file permissions. That's why I readded the ACL documentation used in 3.4 (I've often visited this page in 3.4 to get copy/past the command for new applications). I've made a couple changes from the 3.4 version:See e.g. symfony/demo#795 (comment) for a issue report about this problem in Symfony 4+.