Skip to content

Add another tip to setup permissions #3563

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

Closed
wants to merge 4 commits into from
Closed
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
9 changes: 9 additions & 0 deletions book/installation.rst
Original file line number Diff line number Diff line change
Expand Up @@ -267,6 +267,15 @@ If there are any issues, correct them now before moving on.

Note that using the ACL is recommended when you have access to them
on your server because changing the umask is not thread-safe.

**4. Use the same user for the CLI and the web server**

In development environments, it is a common practice to use the same unix
user for the CLI and the web server because it avoids any of these permissions
issues when setting up new projects. This can be done by editing your web server
configuration (e.g. commonly httpd.conf or apache2.conf for Apache) and setting
its user to be the same as your CLI user (e.g. for Apache, update the User
and Group values).

When everything is fine, click on "Go to the Welcome page" to request your
first "real" Symfony2 webpage:
Expand Down