That fixed it - just deleting to so it defaults to ${RESOURCE} fixed the
issue.
On Thursday, February 4, 2016 at 4:09:36 PM UTC-6, Graham Dumpleton wrote:
>
>
> On 4 Feb 2016, at 10:20 PM, T'ango A'lee <[email protected] <javascript:>>
> wrote:
>
> I am having the following issue with modwsgi and I have NO idea how to fix
> it.
>
> It's outlined here:
>
> https://stackoverflow.com/questions/35096738/2-bitnami-django-projects-running-at-same-time-apache-wsgi
>
> Any help would be very appreciated!!
>
>
> Don't set:
>
> WSGIApplicationGroup %{GLOBAL}
>
> You are forcing both applications to run in the same interpreter context,
> which Django doesn't support because of use of environment variables.
>
> See related information in:
>
> -
> http://blog.dscpl.com.au/2012/10/requests-running-in-wrong-django.html
>
>
> 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 https://groups.google.com/group/modwsgi.
For more options, visit https://groups.google.com/d/optout.
