El sábado 11 de junio de 2011 05:14:37 UTC, Matador escribió:
>
> Hi.
>
> This is for sure not the best answer, but it should work less painful than
> yours,
>
> Instead of:
>
> rm -rf app/cache
> mkdir app/cache
> chmod -R +w app/cache
>
> You can:
>
> rm -rf app/cache/*
>
> This will avoid app/cache from being removed, only its content will.
>
> then:
>
> chmod -R 777 .
>
> This will work if you are in your app's webroot directory, if not just "cd
> yourWebApp/dir/".
>
> This is easier.
>
> Of course, this is not good on production servers, use it only on your dev
> machine.
>
>
If you don't want to deal with acls you could use the sticky bit to keep the
group of the cache dir on it's files:
chgroup www-data app/cache
chmod g+ws app/cache
And set the umask of both your user and the server to 0002 to make any new
file group writeable (in ~/.bashrc and /etc/apache2/envvars):
umask 002
Also, add your user to the www-data group.
--
If you want to report a vulnerability issue on symfony, please send it to
security at symfony-project.com
You received this message because you are subscribed to the Google
Groups "symfony users" group.
To post to this group, send email to symfony-users@googlegroups.com
To unsubscribe from this group, send email to
symfony-users+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/symfony-users?hl=en
