

Move over mod_python, here comes mod_wsgi. - benhoyt
http://blog.micropledge.com/2007/09/the-up-and-coming-mod_wsgi/

======
mattculbreth
I've recently used nginx to reverse-proxy and load balance to both paste and
mongrel. Much easier setup. If you're doing a custom app I tend to think this
is better than running a big Apache up front.

------
cdr
I've been using mod_wsgi for some time (I think trac recommended it).
Interesting that this blog post is getting so much attention.

For apache (and I'm a fan of apache) it doesn't get any better.

~~~
inklesspen
I use mod_proxy to reverse-proxy to paste.httpserver. Much better, IMHO.

------
leisuresuit
or instead use lighttpd with FastCGI and web.py. something like this...
<http://webpy.org/recommended_setup>

~~~
falsestprophet
Even reddit, the developers of web.py, aren't using it anymore.

~~~
kevinl
How do you know it? Http header viewer shows Reddit use lighttpd/1.4.13.

~~~
kirubakaran
He is referring to: <http://reddit.com/info/29qac/comments/c29rpx>

Summary if you don't know the story: aaronsw wrote web.py, founded Infogami
(yc funded) and merged with Reddit. Then he had a falling out with spez and
kn0thing (original founders of Reddit). When Reddit was rewritten, web.py was
not used.

I personally like web.py. Any of you using it for your startup/projects? (May
be we can swap tips) If you are not using web.py for a particular reason, can
you please share that too?

~~~
pg
Steve is too lazy (in the good sense) to have ditched web.py for anything
except legitimate technical reasons.

~~~
kirubakaran
Thank you. This is exactly what I was wondering about and wanted to know from
someone in the know.

~~~
nostrademons
Spez had mentioned, off-handedly, that there tend to be painful bugs in the
main web.py distributions:

<http://programming.reddit.com/info/14v8a/comments/c14y1i>

~~~
kirubakaran
Thanks nos`. Are you still using Pylons? And templates? Would you recommend
MochiKit for js lib?

~~~
nostrademons
Actually, I went with web.py after all. I blame temporary insanity. That, and
web.py was easily understandable without a whole lot of docs to go through,
and I wanted to get _something_ up quickly. We may yet rewrite in Pylons, but
it's low priority, as web.py is working for us. (We also have practically zero
traffic though.)

For templates, we use Mako after having previously used Cheetah, same as the
rewritten Reddit. Mako is a very well-done, well-thought-out library. There
were some things that Cheetah had a lot of trouble with (like unicode support
and fragment libraries) that Mako handles without breaking a sweat.

For JS lib, we eventually settled on jQuery after having tried out Prototype,
YUI, and Mootools (never used Mochikit, sorry). This was largely because that
seems to be where the momentum is these days. Also, jQuery has a very elegant
selector + plugin architecture and a growing collection of plugins. And it's
the first JavaScript library I've seen that's intimately aware of namespace
issues and tries to balance ease-of-use (no silly
YAHOO.widgets.slider.SliderThumb chains here) and not-breaking-anything. This
has been a major issue at my day job - we use several Prototype-dependent
libraries and they _all_ seem to be incompatible with each other, along with
any other JS libraries.

On the downside, jQuery is still fairly immature, so you may have to write
some widgets yourself that are provided with other libraries. That's changing
quickly though, since many people are writing plugins now.

------
tocomment
Can someone just settle Apache vs Lighthttpd for me :-)

