Nginx and uwsgi

Biswas, Pinakee pinakee at
Mon Jun 11 14:01:26 UTC 2012

Hi Roberto,

Thanks for the prompt response. That really helps.

Our major consideration for going with Nginx is performance. 
If we have another process running (a wsgi server with python application) and nginx working as a proxy translating HTTP requests to another protocol (uwsgi, http or fastcgi), won't that be an overhead? 
I was under the impression that the Python application can be embedded in Nginx using Wsgi. 

We would really appreciate your thoughts/suggestions on the above.

Looking forward to your response...

Pinakee Biswas
Director & CTO 

Just watch it ! 

FE- Mail: pinakee at I IWeb: 

 Please don't print this e-mail unless you really need to, this will preserve trees on planet earth. 
The information contained in this message (including any attachments) is confidential and may be privileged. If you have received it by mistake please notify the sender by return e-mail and permanently delete this message and any attachments from your system. Please note that e-mails are susceptible to change and malwares. VVIDIA COMMUNICATIONS PVT LTD. (including its group companies) shall not be liable for the improper or incomplete transmission of the information contained in this communication nor for any delay in its receipt or damage to your system. 

-----Original Message-----
From: nginx-bounces at [mailto:nginx-bounces at] On Behalf Of Roberto De Ioris
Sent: 11 June 2012 19:18
To: nginx at
Subject: Re: Nginx and uwsgi

> Hi,
> We are building a Media Content Management and Delivery Platform based 
> on Python (and python based web framework like Pylons/Pyramid). We are 
> planning to use nginx as the web server.
> We are new to nginx (have prior experience with Apache) and have 
> downloaded 1.2.1. The OS is CentOS.
> We are not sure how uwsgi works with nginx:
> 1.       Do we have to start uwsgi as a separate process?

Yes, but remember: uwsgi is a communication protocol (like http or fastcgi), uWSGI is the application server.
You need to start uWSGI, and configure nginx to speak with it with the protocol of choice (uwsgi, http or fastcgi)

> 2.       There is no option/directives for loading modules in nginx (as it
> is there in Apache).

nginx does not work in that way, but it should be not a problem for you as upstream modules (http, fastcgi, scgi, uwsgi) are compiled in by default.

> 3.       I couldn't find a good documentation on the uwsgi based
> directives.
> The one in nginx wiki is confusing.

you need nothing particular:

include uwsgi_params;
uwsgi_pass <address>;

all the other options are for fine tuning.

I suggest you to start from here:

> Since nginx I think works as a reverse proxy where it forwards HTTP 
> requests to the uwsgi process, how about using something like Cherrypy 
> or PasteHTTPserver? Would there be any difference?

you can proxy nginx to whatever you want/need if the backend speaks one of the supported protocol (http, scgi, fastcgi, uwsgi)

Roberto De Ioris

nginx mailing list
nginx at

More information about the nginx mailing list