> For a while now, I've been using nginx with great success as a remote > proxy server in front of Tomcat, and also in front of PHP via fastcgi. > It's likely that I will require to use it in front of a Django Python > web application soon, and I'm just wondering what the easiest way of > doing this is likely to be. I've read about a number of different ways > of doing this but wby roberto - Nginx Mailing List - English
> On Sat, Jun 04, 2011 at 07:27:07AM +0200, Roberto De Ioris wrote: >> Hi all, >> attached there is an updated patch for adding support for unix socket in >> abstract namespace. >> >> As requested by Igor, the syntax is now >> >> unix:\0foobar >> >> instead of >> >> unix:@foobar >> >> The only relevant note is this paby roberto - Nginx Mailing List - English
Hi all, attached there is an updated patch for adding support for unix socket in abstract namespace. As requested by Igor, the syntax is now unix:\0foobar instead of unix:@foobar The only relevant note is this part of code: + if (saun->sun_path[0] != '\0') { + u->addrs[0].socklen = sizeof(struct sockaddr_un); + } + else { + u->addrs[0].socklen = sizeof(saun-&gby roberto - Nginx Mailing List - English
> On Mon, May 23, 2011 at 07:42:02PM +0200, Roberto De Ioris wrote: >> >> > On Mon, May 23, 2011 at 04:18:30PM +0200, Roberto De Ioris wrote: >> >> (Warning this is Linux only) >> >> >> >> Hi all, the attached path adds support for unix socket in abstract >> >> namespace. >> >> They are special sockets without filesystemby roberto - Nginx Mailing List - English
>>> I hope it can be useful >> >> Thank you for the feature. I think it's better to allow nginx >> configuration >> parser to support "\0" as binary 0. Then this socket may be set as >> >> uwsgi_pass unix:\0funnysock; >> > > I fear it will require changes changes i mean "heavy changes" -- Roberto De Ioris http://by roberto - Nginx Mailing List - English
> On Mon, May 23, 2011 at 04:18:30PM +0200, Roberto De Ioris wrote: >> (Warning this is Linux only) >> >> Hi all, the attached path adds support for unix socket in abstract >> namespace. >> They are special sockets without filesystem correspondence (so you can >> use >> them without thinking about permissions or in chroot). In netstat they >> areby roberto - Nginx Mailing List - English
(Warning this is Linux only) Hi all, the attached path adds support for unix socket in abstract namespace. They are special sockets without filesystem correspondence (so you can use them without thinking about permissions or in chroot). In netstat they are reported with a '@' prefix. For example (using uWSGI): uwsgi -s @funnysock netstat -l unix 2 [ ACC ] STREAM LISTENING 23by roberto - Nginx Mailing List - English
> I've come across an incredibly weird problem with POST responses using > nginx 1.0.1 and uWSGI 0.9.7.2 on CentOS 5.6. > > uWSGI successfully sends the response body to nginx, but nginx seems to > ignore it if both (1) the request method is POST, and (2) the response > length is less than 4052 bytes. The issue doesn't occur when serving > directly using `uwsgi --http`, so I'mby roberto - Nginx Mailing List - English
The second maintainance release for uWSGI 0.9.7 is available. It includes a couple of amazing features that will push you to this new release if you are still under 0.9.6 * 0.9.7.2 [20110406] - new option --touch-reload <file> to reload the stack on <file> modification - --static-map <mountpoint=documentroot> allows to serve static files Example: static-map = /media=djanco/by roberto - Nginx Mailing List - English
The first maintainance release of uWSGI 0.9.7 is available - fixed/improved python stackless support http://projects.unbit.it/uwsgi/wiki/AsyncSupport#SuspendResume - added persistence for queue add --queue-store <file> - forbid daemonizing in vassal mode without this fix emperor will lose connection with vassals - modifier1 30 is available again this is nginx specific - allow pythonby roberto - Nginx Mailing List - English
If i understand correctly you reference a particular view in urls.py with 'appdjango.views' and this does not work. If you simply use 'views' it works. This is a simple pythonpath problem. Add to your configuration file (or commandline as used in the howto) a <pythonpath>/--pythonpath directive set to the directory that contains 'appdjango'. So if you have this layoutby roberto - How to...
This is one of the latest howto: http://django.docshub.org/tutorials/4/deploying-your-django-applications-with-nginx-and-uwsgi It covers all the areas (startup files included). uWSGI is bigger (hundreds of configuration options) than most of the WSGI server out there and this can be a PITA for newcomers, but if you follow this howto you should not have particular problems. Robertoby roberto - How to...