Gertjan:
Python 2.7 is nearing EOL, and I want to migrate the applications to Python 3.7 (the standard Buster Python 3 version). I am seeking advice on how to approach this.
[...]
Graham:
Using mod_wsgi-express behind the original Apache acting as a proxy is one way. Just be warned that mod_wsgi-express is mostly intended for running a single WSGI application. That said, it should use less memory than your main Apache as the configuration it uses is designed to reduce memory over default Apache setup.
If I'm not mistaken, mod_wsgi_express runs in a virtualenv? My apps do as well, so that would work. I would like to use a separate mod_wsgi_express for each application, though, so memory savings I don't see (but are not the goal). Thanks for the links (snipped), it looks very useful!
Graham:
These talk about mod_wsgi-express running in a container, but you don't need to and discussion is still relevant when you don't. You would instead use the `mod_wsgi-express setup-server` command to generate configuration up front and then integrate invocation of 'apachectl' it generates into your system startup system.
I am not opposed to using containers. I noticed the containers you provide stop at Python 3.5. Is there any particular reason for that?
Thanks for your input, 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/qd9158%245hqt%241%40blaine.gmane.org. For more options, visit https://groups.google.com/d/optout.
