Hi,
im wondering if is there any good reason to execute symfony with sudo.
Javi
--
You received this message because you are subscribed to the Google Groups
symfony users group.
To post to this group, send email to symfony-us...@googlegroups.com.
To unsubscribe from this group, send email to
not quite.
Chown the sf_root folder to match your user and pass.
Alecs
On Thu, Jan 7, 2010 at 10:09 PM, Javier Garcia tirengar...@gmail.comwrote:
Hi,
im wondering if is there any good reason to execute symfony with sudo.
Javi
--
You received this message because you are subscribed to
I sometimes need to use sudo when clearing the cache or running fix-perms since
apache usually runs as a different user than the owner of the directory. For
the normal generator related stuff, no.
On Jan 7, 2010, at 3:40 PM, Alexandru-Emil Lupu wrote:
not quite.
Chown the sf_root folder
you can put yourself in www-data group ... :)
On Thu, Jan 7, 2010 at 10:47 PM, Jacob Coby jc...@portallabs.com wrote:
I sometimes need to use sudo when clearing the cache or running fix-perms
since apache usually runs as a different user than the owner of the
directory. For the normal
Apache and Php needs write right to cache dir, this is why it is chmod'ed
777 using project:permissions task.
You probably want apache and php read rights to read .php and other stuff,
and need them write rights for cache and other dynamic-related folders
(upload, etc).
Before Printing, Think
I would only give write permissions by the user running php (most of the
times www-data) to cache, log and the upload directory. All else should be
read only and preferable have another user, like the deployer (nathan in my
case).
Also it's considered very bad practice to give a file/directory
What Nathan said.
Unless your Symfony app is using backtick, passthru, exec or similar operators
to execute shell commands (that MUST be run by root [is there any?]) then you
shouldn't run Symfony as root or via sudo. It's simply bad practice, and
introduces many more attack vectors to
