Any good/bad experiences or alternatives I should check out first?
> --
> You received this message because you are subscribed to the Google Groups "SwiftRiver" group.
> To post to this group, send email to swift...@googlegroups.com.
> To unsubscribe from this group, send email to swiftriver+...@googlegroups.com.
> For more options, visit this group at http://groups.google.com/group/swiftriver?hl=en.
--
http://twitter.com/znmeb http://borasky-research.net
"A mathematician is a device for turning coffee into theorems." -- Paul Erdős
Good point; that's the reason I just opted for Apache+mod_wsgi at the
start, not that there aren't any "better" alternatives but that is
simply the most widely used and best supported.
W/ that said I think if you're going to look for alternatives two
other good options are nginx and litespeed.
However, something tells me your initial instincts will continue to
serve you well in the immediate future. Cheers, -Ali
Never tried litespeed but I'm actually using nginx for the load
balancer and it's working great. I wouldn't mind using that for the
WSGI stuff as well but the WSGI module looks a bit unstable:
http://wiki.nginx.org/NgxWSGIModule
The other alternative is doing this with FastCGI:
http://flask.pocoo.org/docs/deploying/fastcgi/
I don't personally like using FastCGI too much due to hassles with
non-standard environment variables, but I know there are ways to work
around that.