naholyr <[EMAIL PROTECTED]> wrote:

> No one forces permissions, unless you voluntarily make use of "symfony
> fix-perms".

Let's check:

$ symfony new s
[...]
>> chmod 777 /home/user/s/cache
>> chmod 777 /home/user/s/log
>> chmod 777 /home/user/s/web/uploads
>> chmod 777 /home/user/s/symfony
>> chmod 777 web/uploads/assets
$ chmod 755 cache log web/uploads web/uploads/assets symfony
$ symfony app app1
[...]
>> chmod 777 /home/user/s/cache
>> chmod 777 /home/user/s/log
>> chmod 777 /home/user/s/web/uploads
>> chmod 777 /home/user/s/symfony
>> chmod 777 web/uploads/assets
$ chmod 755 cache log web/uploads web/uploads/assets symfony
$ symfony app app2
[...]
>> chmod 777 /home/user/s/cache
>> chmod 777 /home/user/s/log
>> chmod 777 /home/user/s/web/uploads
>> chmod 777 /home/user/s/symfony
>> chmod 777 web/uploads/assets
$ chmod 755 cache log web/uploads web/uploads/assets symfony
(visit our app)
$ find . -perm -666
./cache/app1
./cache/app1/prod
./cache/app1/prod/config
[...]


> Do not hesitate to give the "cache", "log" and "web/uploads"
> directories only the necessary authorizations for writing.

I'm trying. Unfortunately, to make my cache safe I have to hack symfony.

-- 
kjk

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"symfony developers" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/symfony-devs?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to