On Thu, Oct 25, 2007 at 04:05:06PM -0500, [EMAIL PROTECTED] wrote:
> Hi,
>
> I looked through the docs available, and couldn't find a satisfactory answer.
>
> I am trying to restrict access to the "Downloads" section for a specific
> project so that only people who are logged in and are members of the
> project can download them.
>
> Alternatively, it would be acceptable to restrict access to an entire
> project, such that it is only accessible to members of the project. I
> tried marking a project "Private" but that seems to restrict access so
> that no one at all can get to it.
This should restrict access to the group - but at the filesystem
level, so Apache won't be able to serve that download area.
> I'm sure there are multiple ways to do this, but I was wondering if you
> had any recommendations or had an official way to do it.
You can either:
- have members access the download area through SFTP only
- add some ACLs ('setfacl') to the download area so that
Apache/'www-data' can read it even if it's not part of the project
group
- make the project public and implement a replication of the group
members list to a .htpasswd file
Possibly there are other ways.
Private projects are not common in our setups so I can't say there's
an official way to do it :)
--
Sylvain
_______________________________________________
Savane-help mailing list
[email protected]
https://mail.gna.org/listinfo/savane-help
