Regarding having WSGIDaemonProcess outside of vhosts, as explained in the comment I added, it allows you to use the same process to handle requests from multiple vhosts.
As for the rest, I honestly don't remember why or where they came from, I just know that this is probably not all that common (multiple vhosts with different mod_wsgi processes) so sent whatever we have that works in hopes that it'll work for you. Unfortunately I have forgotten how exactly all of this works together. On Thu, Feb 7, 2013 at 1:07 PM, robertlnewman <robertlnew...@gmail.com>wrote: > Thanks for the reply. Very interesting. So you define each > WSGIDaemonProcess outside of the vhosts and then call it from within the > vhost block? What is the advantage of that? Or is it just 6-of-one, > half-a-dozen of another? > > Also, I notice that you are passing a bunch more args to WSGIScriptAlias > (process-group, application-group). I don't see these as available options > in the mod_wsgi docs ( > http://code.google.com/p/modwsgi/wiki/ConfigurationDirectives). The only > option I see that you can pass to WSGIScriptAlias is the URL-path and the > file-path or directory-path: > http://code.google.com/p/modwsgi/wiki/ConfigurationDirectives#WSGIScriptAlias > -- You received this message because you are subscribed to the Google Groups "Django users" group. To unsubscribe from this group and stop receiving emails from it, send an email to django-users+unsubscr...@googlegroups.com. To post to this group, send email to django-users@googlegroups.com. Visit this group at http://groups.google.com/group/django-users?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
