Changes between Version 36 and Version 37 of ServerArrangements

Timestamp:

Nov 28, 2007, 8:46:45 PM (17 years ago)

Author:

Brandon Mercer <yourcomputerpal@…>

Comment:

--

ServerArrangements

@@ -56 +56 @@
  * See [http://www.rkblog.rk.edu.pl/w/p/django-nginx/ Django on nginx] and [http://www.alrond.com/en/2007/mar/01/start-django-with-nginx/ Start Django with nginx].
 
+I've been serving up my django site via nginx for a short while now and wanted to report my setup so that others may give it a shot.  My performance over the previous setup with lighttpd is a bit better.  This setup uses much less cpu and memory to achieve much better throughput and response time.  The simple syntax of the nginx.conf allows you to setup a cluster of backend processes quite easily to handle load.  Currently this is my nginx.conf relevant to my django site.  You can reference the above links for more information about additional options.  
+
+{{{
+
+upstream djangoserv {
+server 127.0.0.1:8801;
+}
+
+server {
+listen 80;
+root /path/to/app;
+server_name test.local.domain;
+access_log /path/to/logs/appname-access.log main;
+error_log /path/to/logs/appname-error.log;
+
+location / {
+                        # host and port to fastcgi server
+                        fastcgi_pass 127.0.0.1:8801;
+                        fastcgi_param PATH_INFO $fastcgi_script_name;
+                        fastcgi_param REQUEST_METHOD $request_method;
+                        fastcgi_param QUERY_STRING $query_string;
+                        fastcgi_param SERVER_NAME $server_name;
+                        fastcgi_param SERVER_PORT $server_port;
+                        fastcgi_param SERVER_PROTOCOL $server_protocol;
+                        fastcgi_param CONTENT_TYPE $content_type;
+                        fastcgi_param CONTENT_LENGTH $content_length;
+                        fastcgi_pass_header Authorization;
+                        fastcgi_intercept_errors off;
+}
+}
+
+}}}
+
+Once you fire up nginx you will need to start your nginx fastcgi processes.  I simply use:
+
+{{{
+
+python2.4 manage.py runfcgi method=threaded host=127.0.0.1 port=8801 
+
+}}}
+
 == Django behind/inside Zope ==