On 6/21/13, Joachim Dreimann <[email protected]> wrote:
> On 21 June 2013 16:22, Olemis Lang <[email protected]> wrote:
>
>> On 6/21/13, Joachim Dreimann <[email protected]> wrote:
>> > On 21 June 2013 04:50, Apache Bloodhound <[email protected]>
>> wrote:
>> >
>> [...]
>> >
>> > I'd be grateful if you could tell me more about:
>> > 1. The use cases for a multi-domain deployment
>>
>> please see http://blood-hound.net
>> You'll notice a number of inconsistencies. I'll be submitting patches
>> soon.
>
>
> That doesn't actually answer my question; all I see is a Bloodhound Error
> page.
That was the result after running MP upgrade , due to the fact that :
1. wiki pages are migrated to *default product*
on a different sub-domain
2. no wiki page is created for new products
(<= though in this case it's the global env)
- no TitleIndex
- no WikiStart
- no Guide/
- no TracIni
- etc ...
3. No redirection to default product happens in this case
like I just mentioned in previous messages .
... is this actually similar to what you might see in a regular BH
installation ?
This is the product we have imported . I'll be working on the next few
days on installing plugins , updating wiki pages , etc ... It's a 0.11
Trac environment last updated on 2009 or so
http://dataviz.blood-hound.net/
> I'm trying to learn under which circumstances a 'regular' Bloodhound
> deployment is not viable, and what makes a multi-domain deployment the best
> option at that point.
>
Well , in this particular case a separate sub-domain for each product
gives it an identity and a separate «cookies space» . So , for
instance , in this particular case there are projects for WebId ,
OpenId , and Mozilla Persona authentication plugins . Therefore it'll
be possible to install those plugins in the corresponding product and
use them in separate domains without clashes , but also to share auth
credentials when needed since they are all under *.blood-hound.net
umbrella .
FWIW sub domains have also been deployed @ github.io afaics .
The important thing regarding your comment in the ticket is that they
all have a different set of wiki pages , tickets , and are independent
projects ... so main nav items and the whole header MUST be scoped .
PS: I'll be taking a look at OpenId plugin soon to install it in there
and also maybe in i.a.o issue tracker, like mentioned in previous
threads. Shortly after 0.6 release I guess it's the right time to do
so.
[...]
--
Regards,
Olemis.
