> On 10 Jun 2019, at 5:43 am, Gertjan Klein <[email protected]> wrote:
>
> [Graham]
>> When you run mod_wsgi-express, you are still running Apache with mod_wsgi,
>> you are just running a separate instance to the main system Apache, with a
>> configuration generated by mod_wsgi-express. So comparing memory usage from
>> the mod_wsgi-express instances to running similar with system Apache only.
>
> Great. I'm finally beginning to understand roughly how this works. It runs an
> instance of the system Apache, but with a compiled-for-it mod_wsgi, and a
> configuration tuned for mod_wsgi. (Correct?)
>
> Is it correct that the only documentation for mod_wsgi-express is on the PyPI
> page?
And various blog posts own my site, plus ensure you run it as:
mod_wsgi-express start-server --help
> I now have a test copy of one of the sites that uses a virtual environment
> with mod_wsgi-express. It works, including the proxy! (Fortunately, the site
> itself needed zero changes from Python 2.7 to 3.7.) There are a few things
> I'm wondering about, though:
>
> * In my previous setup, I used Alias statements in the (main) Apache
> configuration for my static files. It appears these don't work in combination
> with the ProxyPass statement.
Depends on how you set up Proxy statements and the order you have directives in
the Apache configuration file. Impossible to comment without seeing what you
are using. Can you show what you are using?
> I would like to keep using these, though. What I've done now is add an
> Include to the bottom of the generated httpd.conf, including a file that has
> these statements. Is this an appropriate way to do it?
The alternative if can't work out what is wrong with the Apache config for
proxy, is to have mod_wsgi-express host static files by using --url-alias
option.
> * The PyPI page says to add 'mod_wsgi.server' to the installed apps. I didn't
> do that, yet the site works. Is this instruction merely to add the manage.py
> commands? Is there any reason I should prefer these over the generated
> apachectl that I'm using now?
When using as manage.py, it is still generating the Apache configuration. The
difference is that by using runmodwsgi management command, it will
automatically set up mod_wsgi-express to host your Django static media files
and work out where the Django WSGI application entry point is.
See:
http://blog.dscpl.com.au/2015/04/using-modwsgi-express-with-django.html
<http://blog.dscpl.com.au/2015/04/using-modwsgi-express-with-django.html>
http://blog.dscpl.com.au/2015/04/integrating-modwsgi-express-as-django.html
<http://blog.dscpl.com.au/2015/04/integrating-modwsgi-express-as-django.html>
> Thanks again for your help, regards,
> Gertjan.
>
>
>
>
>
> --
> 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.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/modwsgi/qdl8o2%246qa7%241%40blaine.gmane.org.
> For more options, visit https://groups.google.com/d/optout.
--
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.
To view this discussion on the web visit
https://groups.google.com/d/msgid/modwsgi/4CAB4458-D275-4AC4-AE6C-7AD30E4742FB%40gmail.com.
For more options, visit https://groups.google.com/d/optout.
