[kforge-dev] [Fwd: Re: [kforge-user] Modifications]

Wed Feb 7 14:52:00 UTC 2007

FWD FYI

-------- Original Message --------
Subject: 	Re: [kforge-user] Modifications
Date: 	Wed, 07 Feb 2007 14:48:11 +0000
From: 	John Bywater <john.bywater at appropriatesoftwarefoundation.org>
To: 	Christopher Hesse <csh at scourcritical.com>
CC: 	kforge-user at lists.okfn.org
References: 
<78288ee20702062126u42c780b7qde44b70f7cec874c at mail.gmail.com> 
<78288ee20702070132s487e9b51xd0656082832e375a at mail.gmail.com> 
<45C9E3AF.9020305 at appropriatesoftwarefoundation.org>

John Bywater wrote:

> Slightly related to the single host thing: I implemented something 
> called 'uriPrefix' for another domainmodel application (called 
> ScanBooker), which allows the application to be run from something 
> other than /. This was needed because the user couldn't obtain any new 
> FQDNs from their IT manager, who is a point haired boss and very 
> obstructive. As this is a very common situation, I think the current 
> default setup, where you need to setup several FQDNs isn't really 
> adequate.

There is also a mediaPrefix setup in the template context, just after 
the uriPrefix, here:
http://project.knowledgeforge.net/domainmodel/trac/browser/trunk/src/dm/view/base.py#L526

For KForge, we would also need to define a projectPrefix, where all the 
services are rooted. The KForge base view class sets up the template 
context here:

http://project.knowledgeforge.net/kforge/trac/browser/trunk/src/kforge/django/apps/kui/views/base.py#L16

NB Some rather bad names have crept into play here. We do need to review 
a few things.

Bye for now,

J.

_______________________________________________
kforge-user mailing list
kforge-user at lists.okfn.org
http://lists.okfn.org/mailman/listinfo/kforge-user