[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?
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. 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 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?
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.
