8000 [Set-up] Readded ACL file permission docs by wouterj · Pull Request #14327 · symfony/symfony-docs · GitHub
[go: up one dir, main page]

Skip to content

[Set-up] Readded ACL file permission docs #14327

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Oct 7, 2020

Conversation

wouterj
Copy link
Member
@wouterj wouterj commented Oct 3, 2020

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 using chmod -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:

  • I've reordered to put the most recommended method (ACL) as first;
  • I've dropped macOS. Both these commands a very much 90% use-case fit commands, so they were a bit maintenance heavy - which means I wanted to reduce the list. I don't think many people run Symfony in production on a macOS server.

See e.g. symfony/demo#795 (comment) for a issue report about this problem in Symfony 4+.

@javiereguiluz
Copy link
Member

Thanks Wouter! This is now merged. I agree with all your proposed changes. However, while merging we did some other changes:

  • Some headings were updated to make them easier to scan and more Google-friendly
  • I removed the explicit reference to Doctrine query cache because Doctrine cache drivers are deprecated and they use Symfony cache ... so if you use a filesystem-based cache, it affects to everything (Doctrine or not)

@wouterj wouterj deleted the setup-file-permission branch October 7, 2020 10:45
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants
0