Skip to content
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

Add another tip to setup permissions #3563

Closed
wants to merge 4 commits into from
Closed

Add another tip to setup permissions #3563

Changes from 1 commit
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
8 changes: 8 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,14 @@ 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 CLI and HTTP**
Copy link
Member

Choose a reason for hiding this comment

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

... the CLI and the web server


It is a common practice to use the same unix user for CLI and HTTP. It avoids
Copy link
Member

Choose a reason for hiding this comment

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

for the CLI and the web server

Copy link
Member

Choose a reason for hiding this comment

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

I might clarify even more:

... for the CLI and the web server, because it avoids any of these permissions issues. This is done by...

Copy link
Member

Choose a reason for hiding this comment

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

I suppose if we're going to mention this, we should say something more like:

In development environments, you can also choose to use the same...

Because isn't there a potential security issue with running Apache as your CLI user (i.e. Apache can modify a lot more files on your system)?

Copy link
Member

Choose a reason for hiding this comment

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

Yes, I see your note below about the dev environment now :) - let's still change the note above a little bit so that people are aware.

typing commands when setting up new projects. This is done by editing your
Apache configuration file ``httpd.conf`` and update the user and group values
Copy link
Member

Choose a reason for hiding this comment

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

These are called User and ~group` (capital letters) I believe.

from ``www-data`` to your CLI user. Obviously, this is only recommended in dev
environnement.
Copy link
Contributor

Choose a reason for hiding this comment

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

typo, it should say environment

Copy link
Contributor

Choose a reason for hiding this comment

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

this is not needed for a development environment imo, i never do this for instance, i have never done it neither in ubuntu nor in mac

Copy link
Contributor Author

Choose a reason for hiding this comment

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

@cordoval I agree this is not needed, it is just another option among others :)


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