On 7 July 2010 01:15, Aljoša Mohorović <[email protected]> wrote: > On Thu, Jun 17, 2010 at 10:54 AM, Graham Dumpleton > <[email protected]> wrote: >> Followup to this thread is okay. > > i didn't have time to properly read docs and test configurations (hope > i'll have time next week) but i have some questions and would > appreciate any comments. > > silverlining approach to use a single wsgi file to handle app > revisions is interesting and i was wondering if anybody would like to > comment pros/cons on using apache config vs. wsgi file to handle app > revisions? > > i've been playing with VirtualDocumentRoot and it looks ok but i can't > find what is the problem when used instead of VirtualHost? > i did get an impression that for some reason i shouldn't mix > VirtualHost and VirtualDocumentRoot although i'm not sure why (am i > just wrong here?). > if i use VirtualDocumentRoot as default config can individual domains > (or subdomains) be configured separately?
I think (cant remember for sure), if you are using VirtualDocumentRoot at global scope in Apache configuration you cant use VirtualHost at the same time. If however you need to use VirtualHost, you can still use VirtualDocumentRoot inside of the VirtualHost to map to varying document root where you have a ServerAlias that matches multiple names for that VirtualHost. 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.
