Overall I would rate it as "not", but the only system that still had major
issues is the central permissions stuff. As long as you are only using the
project index, you should be fine.

--Noah

> -----Original Message-----
> From: [email protected] [mailto:[EMAIL PROTECTED]
> On Behalf Of lfrancis
> Sent: Wednesday, July 16, 2008 5:56 AM
> To: Trac Users
> Subject: [Trac] Re: Restricting project listing to ip range b/w
> segregated projects?
> 
> 
> Thanks Noah, sounds like that could fit the bill -- how close is
> TracForge to being ready for Trac .11?
> 
> -Lewis
> 
> On Jul 15, 8:55 pm, "Noah Kantrowitz" <[EMAIL PROTECTED]> wrote:
> > > -----Original Message-----
> > > From: [email protected] [mailto:trac-
> [EMAIL PROTECTED]
> > > On Behalf Of lfrancis
> > > Sent: Tuesday, July 15, 2008 5:28 PM
> > > To: Trac Users
> > > Subject: [Trac] Restricting project listing to ip range b/w
> segregated
> > > projects?
> >
> > > We want to allow our clients access to our internal Trac .11 multi-
> > > project ticketing system, but we want to prevent one client from
> > > accessing another client's project environment, while still
> allowing
> > > our team members easy access to any project. Right now this 'easy
> > > access' is via the project listing url and a link on each
> environment
> > > back to the project listing.
> >
> > > My initial thinking is to wrap the project listing code in an ip
> range
> > > check and print the list if the ip is one of our internal ip
> addresses
> > > -- has anyone done this?  I'm guessing there's a fairly easy way to
> > > implement this, but I'm not a Python developer and my cursory
> review
> > > of Python docs have so far left me scratching my head.
> >
> > > But perhaps there's an easier scheme that I'm overlooking?  What do
> > > all of you do when tasked with running multiple projects and
> wanting
> > > to keep your users segregated?
> >
> > TracForge supports doing a normal permission check, so you could do
> this
> > with a policy plugin. Just look at the ones in sample-plugins/ as an
> > example.
> >
> > --Noah
> 


--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "Trac 
Users" 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/trac-users?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to