I greatly appreciate your input and I got my “Hello, World” app working, but I ended up up going a different route. Details below in case anyone else runs across this in the future.
Since you pointed out that I would be incapable of have multiple versions of python running even with virtual environments, I decided there was no practical reason to install mod_wsgi into my app’s virtual environment versus a global installation. after all, I intend to have at least four python3 based flask apps running on this server in the next few months. So, I went with the CMMI method instead. If/when I upgrade python beyond python3.6 I’ll just recompile mod_wsgi and update my apps as needed. I followed your documentation for the CMMI method over at http://modwsgi.readthedocs.io/en/develop/user-guides/quick-installation-guide.html. It went smoothly until I reached the section titled “Loading Module into Apache”. The apache2.4 documentation indicates that “httpd.conf” is no loner used for loading modules. Rather I needed to create a “wsgi.load” file and drop it into apache’s /mods-available directory. After that all it took was a simple “a2enmod wsgi” command followed by an apache restart and the app was running. I used the virtual environment documentation at http://modwsgi.readthedocs.io/en/develop/user-guides/virtual-environments.html running in single application daemon mode and a using a .wsgi file located in my app’s root directory. Further documentation regarding .wsgi files at http://flask.pocoo.org/docs/0.12/deploying/mod_wsgi/ -- 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.
