Comment 6 for bug 1162400

Hi Adrian,

We're moving from mod_wsgi to gunicorn to coalesce around a single wsgi container. Other services deployed into the Canonical DC cloud (prodstack) are also using gunicorn. This reduces the number of things that the webops team have to be experts in and lets us share best practices.

It wasn't my decision to pick gunicorn, so I can't speak to any performance or debugging benefits over mod_wsgi.

Hope that helps to clarify.

Slimmer is available in universe in precise, so we could indeed use that for inline css/js (though I'm inclined to push inline content out into static files). For static js files, yuicompressor is used by at least U1. It's also pluggable into django-static, so we could use it for inline content as well at the cost of it being slower than slimmer.

U1 doesn't use django-static, but want to move in that direction:
"We do it the heavy-handed way: have a rewrite rule in apache to do /static/<revno>/ -> /static internally, and include <revno> in the url when generating the html. We should eventually move to something like django-static, but not in the short-term plans."

django-static isn't packaged, so we'd have to sort that out (for precise) if we are to use it.