Chris Hoeppner wrote:
> Well, just to know. What are you using? This should also be useful for
> my "little" project, the django deployer, still unnamed.

I had the most frustration with a software in recent memory trying to use
lighttpd.  Config syntax was utterly weird and the docs conflicted with actual
behavior.  I dumped it for nginx.

Nginx has been a near dream.  The syntax makes sense(YMMV), and it has done what
I wanted without hassle.

Use it to:
   - serve static and proxy to three separate django-servers(on different ports)
for development
   - serve static and proxy to mod_python/apache a test server
   - serve static and proxy to mod_python/apache a production server

I'm familiar with apache/mod_python so the backend is that rather than something
"trendier".

When traffic becomes an issue, one problem we are glad to have :) we'll do some
stress/load testing. Probably comparing ngix->apache/mod_python to ngix->fcgi


nginx   -> http://wiki.codemongers.com/Main
my site -> http://StoryMash.com

I really can't recommend nginx enough,
norm


--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"Django users" group.
To post to this group, send email to django-users@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/django-users?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to