Cleanest & Fastest server setup for Django [closed]

I'm about to deploy a mediumsized site powered by Django. I have a dedicated Ubuntu Server.

I'm really confused over which serversoftware to use. So i thought to myself: why not ask stackoverflow.

What i'm looking for is:

• Easy to set up
• Fast and easy on resources
• Can serve mediafiles
• Able to serve multiple djangosites on same server
• I would rather not install PHP or anything else that sucks resources, and for which I have no use for.

I have heard of mod_wsgi and mod_python on Apache, nginx and lighty. Which are the pros and cons of these and have i missed someone?

@Barry: Somehow i feel like Apache is to bloated for me. What about the alternatives?

@BrianLy: Ok I'll check out mod_wsgi some more. But why do i need Apache if i serve static files with lighty? I have also managed to serve the django app itself with lighty. Is that bad in anyway? Sorry for beeing so stupid :-)

UPDATE: What about lighty and nginx - which are the uses-cases when these are the perfect choice?

Since I was looking for some more in-depth answers, I decided to research the issue myself in depth. Please let me know if I've misunderstood anything.

Some general recommendation are to use a separate webserver for handling media. By separate, I mean a webserver which is not running Django. This server can be for instance:

• Lighttpd (Lighty)
• Nginx (EngineX)
• Or some other light-weight server

Then, for Django, you can go down different paths. You can either:

• Serve Django via Apache and:

  • mod_python

    This is the stable and recommended/well documented way. Cons: uses a lot of memory.

  • mod_wsgi

    From what I understand, mod_wsgi is a newer alternative. It appears to be faster and easier on resources.

  • mod_fastcgi

    When using FastCGI you are delegating the serving of Django to another process. Since mod_python includes a python interpreter in every request it uses a lot of memory. This is a way to bypass that problem. Also there is some security concerns.

    What you do is that you start your Django FastCGI server in a separate process and then configures apache via rewrites to call this process when needed.

Or you can:

• Serve Django without using Apache but with another server that supports FastCGI natively:

  (The documentation mentions that you can do this if you don't have any Apache specific needs. I guess the reason must be to save memory.)

  • Lighttpd

  This is the server that runs Youtube. It seems fast and easy to use, however i've seen reports on memoryleaks.

  • nginx

  I've seen benchmarks claiming that this server is even faster than lighttpd. It's mostly documented in Russian though.

Another thing, due to limitations in Python your server should be running in forked mode, not threaded.

So this is my current research, but I want more opinions and experiences.

I'm using Cherokee.

According to their benchmarks (grain of salt with them), it handles load better than both Lighttpd and nginx... But that's not why I use it.

I use it because if you type cherokee-admin, it starts a new server that you can log into (with a one-time password) and configure the whole server through a beautifully-done webmin. That's a killer feature. It has already saved me a lot of time. And it's saving my server a lot of resources!

As for django, I'm running it as a threaded SCGI process. Works well. Cherokee can keep it running too. Again, very nice feature.

The current Ubuntu repo version is very old so I'd advise you use their PPA. Good luck.