https://stackoverflow.com/questions/18048318/apache-mod-wsgi-vs-nginx-gunicornThere are several fantastic tutorials online regarding apache2 and mod_wsgi. A simple google search with the keywords apache2 and mod_wsgi should grant you a couple. What I did when I deployed on nginx and gunicorn (which I highly recommend over apache combinations. Read SO post) was I compared two tutorials and made sure they were pretty similar.
Besides preference in performance and how requests are served etc. etc., I just found nginx + gunicorn much easier to setup. Good luck!
(Now my tangent recommendation. Hope the above helped!)
If you get stuck somewhere with apache2 and mod_wsgi, try out nginx and gunicorn with these links:
(BEFORE YOU GO ON. There is an error in the SECOND tutorial (the digitalocean one. When doing gunicorn --bind
0.0.0.0:8000 myproject.wsgi, make sure you type in gunicorn --bind
0.0.0.0:8000 myproject.wsgi:application).
(Has a conclusion which'll help you debug stuff. If you get stuck or you don't see a symlink being created, do sudo systemctl stop gunicorn && sudo systemctl disable gunicorn && sudo systemctl enable gunicorn && sudo systemctl start gunicorn . Or you you can switch gunicorn with nginx.)
They both use postgres for database, but you can skip those steps if you'd like. No harm.