On Fri, 2011-04-15 at 16:36:31 +0300, Audrius Kažukauskas wrote: > I was doing the following: > > $ uwsgi --ini-paste /path/to/production.ini --pidfile /path/to/pid > > And in production.ini there was included: > > [uwsgi] > processes = 1 > socket = /path/to/socket-file > home = /path/to/virtualenv > master = true > > This was done using uWSGI 0.9.6.x. I'll try this now with 0.9.7.x to > see if it still works.
Used the following for one of my personal projects, since I don't have any HTTP server installed at the moment: $ uwsgi --plugins python26,http --http :8080 --ini-paste development.ini development.ini contains [uwsgi] section identical to the one from my previous email (of course, with the real paths). Works like a charm with freshly built virtualenv for Pylons 1.0 application. I forgot to tell that I was using nginx before, but it shouldn't make any difference. HTH, -- Audrius Kažukauskas
pgpf35ctqIFeH.pgp
Description: PGP signature
_______________________________________________ uWSGI mailing list [email protected] http://lists.unbit.it/cgi-bin/mailman/listinfo/uwsgi
