2009/1/6 Todd O'Bryan <[email protected]>: > > On Mon, Jan 5, 2009 at 5:34 AM, Graham Dumpleton > <[email protected]> wrote: >> >> You could have just used: >> <Location /wikis> >> WSGIProcessGroup wikis >> WSGIApplicationGroup %{GLOBAL} >> </Location> >> > Actually, I tried this and Moin got confused and thought that the wiki > name, (the 'abc' etc. in my example) was the name of a page. Thus when > I went to /wikis/abc it tried to load the 'abc' page in the 'abc' > wiki. Links also didn't work because it tried to link to > '/wikis/LinkText' instead of '/wikis/abc/LinkText'.
I can't see how this would affect anything as it doesn't come into play when mapping URL to script file and determining the rather important value of SCRIPT_NAME in WSGI environment. All this Location block would have been doing is determining which processes and which sub interpreter within the process it would be executed within. >> I actually also question your use of WSGIScriptAliasMatch. One could >> also have said: >> >> WSGIScriptAlias /wikis /path/to/moin.wsgi >> > As I said, I had to include the wiki name in the match so that it got > ignored as part of the URL that Moin tries to deal with. Which is where SCRIPT_NAME possibly then comes into play. For above, probably sets it to '/wikis', where as for your original pattern was setting it differently for each wiki instance, ie., '/wiki/abc', '/wiki/d', etc. This distinction must be import to MoinMoin. Would still like to see you try setting WSGIProcessGroup/WSGIApplicationGroup in Directory container. Graham --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "modwsgi" 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/modwsgi?hl=en -~----------~----~----~----~------~----~------~--~---
