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.

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

Closed
wants to merge 4 commits into from
Closed

Add another tip to setup permissions #3563

Changes from 3 commits
Commits
Show all changes
4 commits
Select commit Hold shift + click to select a range
1aaa291
Add another tip to setup permissions in dev environnement.
tony-co Feb 10, 2014
b955d99
Update installation.rst
tony-co Feb 10, 2014
625369a
Updated tip with latest comments
tony-co Feb 18, 2014
0d5bcd7
Rephrase
tony-co Mar 19, 2014
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
10 changes: 10 additions & 0 deletions book/installation.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -267,6 +267,16 @@ 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 is done by editing your Apache
configuration file ``httpd.conf`` and updating the User and Group values
from ``www-data`` to your CLI user. Obviously, this is only recommended in
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This can be done by editing your web server configuration (e.g. commonly httpd.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).

What do you guys think? I wanted to keep it short, but mention Apache as just an example

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This sounds good to me. Maybe one last thing that I'm sure @lyrixx will mention is that on some distributions the default conf file is named apache2.conf so should we mention both?

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

ok for me ;) an yes for the apache2.conf

development environment as you do not want to give Apache full control over
your whole production system.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I agree with @lyrixx that we should just avoid talking about production - so remove the last sentence. We already start with "In development environments", so I think we're good :).


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