On Dec 3, 4:52 pm, Kyle Fox <[EMAIL PROTECTED]> wrote:
> Yes, we're using mod_wsgi But I'm not sure that approach saves us
> much because I'd still need to write a WSGI file for every site.
>
> (This might be because of my lack of mod_wsgi-fu, but wouldn't I also
> need a VirtualHost directive for each site, pointing it to the
> appropriate WSGI file?)
Yes, you would still need a separate VirtualHost, or you would need to
mount the separate Django instances at different sub urls of the same
site. You would preferably have a separate daemon process for each
instance as well, because for large number of sites, having them in
separate sub interpreters of embedded mode, isn't really a good idea
because of the much large memory requirements.
If this really isn't what you want and you truly are instead trying to
run it all in a single Django instance, then suggestion wouldn't help
much and you would have to go back to investigating method which
allowed you to override settings on a per request basis.
The issue is that it wouldn't be appropriate to allow all settings to
be overridden on a per request basis as some would have to be global
regardless.
I'll let others comment on what could be done as Django internals
isn't my area.
Graham
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Django developers" group.
To post to this group, send email to django-developers@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/django-developers?hl=en
-~----------~----~----~----~------~----~------~--~---
