[Radiant] Getting Radiant rolling on a fresh Dapper install with Deprec

[Aitor Garay-Romero]

    The important thing is that the Radiant (Rails) process must have write
permissions to that directory.  Both the chmod and chgrp do the job.  For me
seems that the chgrp you did is more clean.  Security is a though topic, but
in your case i wouldn't be worried too much, it's just the temp directory.

    /AITOR

On Dec 6, 2007 12:53 AM, Andrew Neil <andrew.jr.neil at googlemail.com> wrote:

>
> > The easiest way to solve this is to try a "chmod a+w -R", on /var/
> > www/apps/nomore/current/cache/ .
>
> OK, I tried that and it worked. So that appears to have sourced the
> problem.
>
> > But be aware of security issues.
>
> Indeed. Here is the output from running 'ls -al' from my app
> directory on the server (after resetting permissions with  "chmod 775
> cache"):
>
> drwxrwxr-x  3 deploy deploy       4096 Dec  5 23:09 cache
> drwxrwxr-x  4 deploy deploy       4096 Dec  5 23:09 config
> drwxrwxr-x  3 deploy deploy       4096 Dec  5 23:09 db
> drwxrwxr-x  7 deploy deploy       4096 Dec  5 23:09 public
> drwxrwxr-x  5 deploy deploy       4096 Dec  5 23:09 script
> drwxrwxr-x  6 deploy app_nomore   4096 Dec  5 23:09 tmp
> drwxrwxr-x  5 deploy deploy       4096 Dec  5 23:09 vendor
>
> I notice that the tmp/ directory has different ownership group from
> all other directories. So I tried running "sudo chgrp app_nomore
> cache/", which changed to:
>
> drwxrwxr-x  3 deploy app_nomore   4096 Dec  5 23:09 cache
> ...
> drwxrwxr-x  6 deploy app_nomore   4096 Dec  5 23:09 tmp
>
> Which also works. Does this avoid the security issues mentioned above?
>
> I guess I just have to work out how to add that command to my
> deploy.rb file as a capistrano task now.
>
> Thanks for the tip Aitor!
>
> Drew
> _______________________________________________
> Radiant mailing list
> Post:   Radiant at lists.radiantcms.org
> Search: http://radiantcms.org/mailing-list/search/
> Site:   http://lists.radiantcms.org/mailman/listinfo/radiant
>