On 26/04/2014, at 3:05 AM, [email protected] wrote:
> I figured out my original problem by following your suggestion of verifying
> the right mode/interpreter context.
> When I loaded http://server/root/client1/appA it was getting the right daemon
> process, but http://server/root/client1/appA/ or any child path, it was
> running in embedded mode.
> So something wasn't working with my <Location /root/*/A> block. The docs I
> can find say it should have worked recursively so not sure why it wasn't.
>
> I wanted to eliminate the location block anyways once you told me about those
> extra options I can pass to WSGIScriptAlias.
> I first tried them with WSGIScriptAliasMatch but got this error:
>
> ... waiting Syntax error on line 30 of /etc/apache2/conf.d/wsgi.conf:
> Invalid option to WSGI script alias definition.
>
> I then converted by WSGIScriptAliasMatch to a bank of N WSGIScriptAlias's
> like so:
>
> WSGIScriptAlias /root/client1/A /wsgi/shared/A/A.wsgi \
> process-group=A application-group=%{GLOBAL}
> WSGIScriptAlias /root/client2/A /wsgi/shared/A/A.wsgi \
> process-group=A application-group=%{GLOBAL}
> WSGIScriptAlias /root/client3/A /wsgi/shared/A/A.wsgi \
> process-group=A application-group=%{GLOBAL}
> WSGIScriptAlias /root/client4/A /wsgi/shared/A/A.wsgi \
> process-group=A application-group=%{GLOBAL}
> WSGIScriptAlias /root/client5/A /wsgi/shared/A/A.wsgi \
> process-group=A application-group=%{GLOBAL}
> WSGIScriptAlias /root/client6/A /wsgi/shared/A/A.wsgi \
> process-group=A application-group=%{GLOBAL}
>
> It sort of sucks having to duplicate all those config lines, but I guess it's
> not as bad as the alternative,
> and everything is working as I expect now with no mixing of environments, so
> I got that going for me.
If using WSGIScriptAliasMatch you would need to likely have used something like:
WSGIScriptAliasMatch ^/root/[^/]*/A(/?.*) /wsgi/shared/A/A.wsgi$1 \
process-group=A application-group=%{GLOBAL}
That is, you need to match the full URL and substitute the tail back on the end
of the target.
What I can't remember is if that screws up SCRIPT_NAME in WSGI environ
specifying the mount point.
Graham
--
You received this message because you are subscribed to the Google Groups
"modwsgi" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/modwsgi.
For more options, visit https://groups.google.com/d/optout.
