Hi, i have some similar (well, maybe not, but the permission problem is similar). What works fine is the use of access control lists (ACL), provided by the ACL-tools (getfacl, setfacl). All of the files owner and group can remain the same as they are originally installed.
Additionally, you can grant access to the user/group www-data (or what else you can imagine) to specific files and directories (attention here, you don't want to grant access to www-data on the whole /usr/local structure). In my case, all users on the system want to deploy their own django-app, so i made these directories accessible to the web server via setfacl. Cheers, [also] David 2010/11/25 David Taylor <[email protected]> > On 25/11/10 21:42, David Taylor wrote: > >> >> I'll write up some instructions on getting ispconfig working with cherokee >> and post them in a follow-up reply. >> > > > Done. Check out: > > http://www.cloudartisan.com/2010/11/using-ispconfig-with-cherokee/ > > > Cheers, > David. > > http://www.cloudartisan.com > _______________________________________________ > Cherokee mailing list > [email protected] > http://lists.octality.com/listinfo/cherokee > -- mail: [email protected] web: bluenode.de
_______________________________________________ Cherokee mailing list [email protected] http://lists.octality.com/listinfo/cherokee
