Green Unicorn

6 views
Skip to first unread message

Charl van Niekerk

unread,
Dec 7, 2011, 2:16:28 PM12/7/11
to SwiftRiver
Currently I'm still using Apache and mod_wsgi for RiverID but am
strongly considering moving over to this:

http://gunicorn.org/

Any good/bad experiences or alternatives I should check out first?

M. Edward (Ed) Borasky

unread,
Dec 18, 2011, 1:52:16 AM12/18/11
to swift...@googlegroups.com
Call me paranoid, but any web server other than Apache is gonna need a
*lot* of support infrastructure and a humongous team and preferably a
business model before I'm going to expend any energy learning about
it. I heard great things about Mongrel and I hear great things about
Node.js, but really, I don't trust "new stuff" much these days.

> --
> 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

Charl van Niekerk

unread,
Dec 18, 2011, 6:08:40 AM12/18/11
to swift...@googlegroups.com
2011/12/18 M. Edward (Ed) Borasky <zn...@borasky-research.net>:

> Call me paranoid, but any web server other than Apache is gonna need a
> *lot* of support infrastructure and a humongous team and preferably a
> business model before I'm going to expend any energy learning about
> it. I heard great things about Mongrel and I hear great things about
> Node.js, but really, I don't trust "new stuff" much these days.

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.

Ali-Reza Anghaie

unread,
Dec 18, 2011, 12:45:48 PM12/18/11
to swift...@googlegroups.com
And I think, for this ~type~ of project in particular, that's the
route to stick to. You're not going to have a situation where any
given localized linux distribution, or Wintel bundle, or even Mac,
aren't going to have a fairly straight-forward way of setting this up.
Go elsewhere, introduce even a few hickups, and it gets perceived as a
boutique project about the tech and not about the data/purpose.

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

Charl van Niekerk

unread,
Dec 19, 2011, 5:31:36 AM12/19/11
to swift...@googlegroups.com
2011/12/18 Ali-Reza Anghaie <a...@packetknife.com>:

> W/ that said I think if you're going to look for alternatives two
> other good options are nginx and litespeed.

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.

Reply all
Reply to author
Forward
0 new messages