Hey Stephan,
Your insight is pretty much everything I got out of researching too--right
down to the links.  Too bad.  I'm no sys admin and I hate managing more
servers than needed.

I'm glad that I know I'm not missing out on anything though.

Thanks for the info,
Nathan

2009/7/1 Stephan Altmueller <step...@klaravision.com>

> Hi Nathan,
>
> We use nginx as our main (and only) web front-end, so I had the same
> question.
>
> I have looked into mod_wsgi and found these two blog posts (not directly
> answering your question though)
>
> http://tomster.org/blog/nginx-mod-wsgi-python2.4
>
> http://blog.dscpl.com.au/2009/05/blocking-requests-and-nginx-version-of.html
>
> Especially the last one (by the author of Apache mod_wsgi) makes a
> good argument why mod_wsgi (at least in it's current incarnation) might
> not be a good choice.
>
> The point is really that nginx uses asynchronous non-blocking IO, while
> bfg blocks to load the model.
>
> I have thought about what it would take to make nginx work with bfg
> (or similar WSGI frameworks). I think hat you would have to
> move around the architecture significantly to incorporate non-blocking I/O.
>
> It also seems mod_wsgi for nginx is not really maintained.
>
> I am still in the development phase, but right now I am planning on
> proxy'ing from nginx to an application sever.
> I have seen several comments that point to FastCGI as a good option.
> You could also use Apache with mod_wsgi as your app server and proxy
> to it.
>
> I have found quite a lot of information (message boards etc.) on how
> to proxy from nginx to Pylons apps. Almost all of that should also
> apply to bfg.
>
> Hope this helps, would like to hear if you find out anything else.
>
>  -- Stephan
>
> Nathan Van Gheem wrote:
> > Anyone ever deploy repoze.bfg on nginx with mod_wsgi?  Right now I'm
> > just using proxy_pass to the paster serve for repoze.bfg, but it just
> > seems more natural if this could be done using mod_wsgi.
> >
> > Any thoughts?
> >
> > Thanks,
> > Nathan
> >
> >
> > ------------------------------------------------------------------------
> >
> > _______________________________________________
> > Repoze-dev mailing list
> > Repoze-dev@lists.repoze.org
> > http://lists.repoze.org/listinfo/repoze-dev
>
> _______________________________________________
> Repoze-dev mailing list
> Repoze-dev@lists.repoze.org
> http://lists.repoze.org/listinfo/repoze-dev
>
_______________________________________________
Repoze-dev mailing list
Repoze-dev@lists.repoze.org
http://lists.repoze.org/listinfo/repoze-dev

Reply via email to