> On 2 Jun 2019, at 4:17 am, Gertjan Klein <[email protected]> wrote: > > Hi, > > I have a VPS that runs four WSGI applications of varying importance. These > run on Debian Buster, with the standard Debian versions of the various > components: Python 2.7.16, Apache/2.4.38 (Debian), mod_wsgi 4.6.5-1. The > sites use Django and Flask. > > 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. > > I could upgrade all applications on my development environment, and then do > the server in one go. However, I would prefer to get rid of the > interdependency of these applications: they currently all need to use the > same mod_wsgi, and hence Python. > > Two approaches I can think of to do that are Docker and, perhaps, mod_wsgi > express. I'd like to keep things as light-weight as possible (these are tiny > sites, with only a few users). > > What would be the best way to go here?
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. There is discussion about how to use mod_wsgi-express behind Apache as a proxy in: * http://blog.dscpl.com.au/2015/06/proxying-to-python-web-application.html <http://blog.dscpl.com.au/2015/06/proxying-to-python-web-application.html> * http://blog.dscpl.com.au/2015/07/redirection-problems-when-proxying-to.html <http://blog.dscpl.com.au/2015/07/redirection-problems-when-proxying-to.html> 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. 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. To view this discussion on the web visit https://groups.google.com/d/msgid/modwsgi/F3CA4210-F34E-4BB4-BA87-F1CD020FCA1F%40gmail.com. For more options, visit https://groups.google.com/d/optout.
