Skip to content

No more permissions craziness! #8795

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.

Sign up for GitHub

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 3 commits into from
Dec 1, 2017
Merged

No more permissions craziness! #8795

Changes from 1 commit
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
d50d0e6
Bye bye permissions craziness
weaverryan Nov 30, 2017
327db54
adding details about 777
weaverryan Dec 1, 2017
32a2516
Minor fixes
javiereguiluz Dec 1, 2017
File filter

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Prev Previous commit
Next Next commit
adding details about 777
  • Loading branch information
@weaverryan
weaverryan authored Dec 1, 2017
commit 327db54cb15210737f3dcd0fc4e8ae8bf512671f
3 changes: 2 additions & 1 deletion setup/file_permissions.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -15,4 +15,5 @@ was writable. But that is no longer true! In Symfony 4, everything works automat

If you decide to store log files on disk, you *will* need to make sure your
logs directory (e.g. ``var/logs``) is writable by your web server user and
terminal user.
terminal user. One way this can be done is by using ``chmod 777 -R var/logs``.
Just be aware that your logs are readable by any user on your production system.