Now if you would prefer to launch your applications behind their own uWSGI process you can simply change (or duplicate) the uWSGI configuration like so:

<uwsgi>	 	 
    <socket>127.0.0.1:3031</socket>
    <pidfile>/var/run/uwsgi.pid</pidfile>
    <processes>4</processes>
    <master/>
    <uid>www-data</uid>
    <gid>www-data</gid>
    <daemonize>true</daemonize>
</uwsgi>

Then you can simply remove the UWSGI_SCRIPT and UWSGI_CHDIR parameters from your Nginx configuration, and point uwsgi_pass directly at the listening address for that specific application.

For more configuration options regarding the uWSGI server check out their Documentation

Additional Resources

Nginx Wiki – Full of documentation and guides contributed by the community.
Circuits – Circuits Documentation at Python.org.
Genshi – A very useful Python library for processing HTML, XML and other text output.
SQLAlchemy – Gives Python application developers the full power and flexibility of SQL.

Remember that for Python 3, responses need to be sent as byte instances. This can either be done with typing it as bytes for example b”A string”, or encoding “A string”.encode(‘utf-8’).

• Previous Entry: Adding Google Sitemap CPanel Firewall Exception