I found this a bit confusing.
Being somewhat new to mod_wsgi and needing to perform a Centos/Django build it can be quite frustrating chasing down direct configuration methods.
I start down a path and in the middle I get placed on a different config explanation that derails me. Along with doubt as I keep finding mixed information between sources.
Currently best I can tell is take notes on every aspect as you go and mark the ones you actually need to use; then go back and hopefully piece it together.
I believe in general, most people would use httpd/apache as installed by sys admins managing the ssl and it providing other services.
I find a lot more resources on installing mod_wsgi than using the pip install method.
I am trying to follow the pip install method as a best process but it lacks concise information. Now I see I should be using Apache as a proxy and not loading wsgi :/
Also I would think most people using this are using Django. But that is just my reasons.
If there is a hidden update document that forks on configuration than what I have found perhaps?
As eventually I will need to provide results in getting this to production and may need to find alternatives.
Is the PIP install method a production method?