summaryrefslogtreecommitdiffstats
path: root/patchwork.wsgi
diff options
context:
space:
mode:
authorMartin Krafft <madduck@madduck.net>2010-01-31 02:32:45 +0100
committerJeremy Kerr <jk@ozlabs.org>2010-08-10 11:49:35 +0800
commit2ad2af87e5e438f26ae1f26d21d02052f75cc091 (patch)
tree1524f1ba1ac9817706fbe3f7408fb78725da3c83 /patchwork.wsgi
parentef3b7b60bbfbcd7b61e3a04797d110ee19fc4506 (diff)
downloadpatchwork-2ad2af87e5e438f26ae1f26d21d02052f75cc091.tar.bz2
patchwork-2ad2af87e5e438f26ae1f26d21d02052f75cc091.tar.xz
lib/apache2: Add WSGI Handler
Patchwork/Django can be run directly with WSGI, which is bound to be faster and less complex than FastCGI. This patch provides the necessary Apache configuration and the WSGI handler, as well as an update to the docs. Since python-flup is deprecated and WSGI supersedes FastCGI, it should be(come) the preferred method. Hence I documented it first. For the xmlrpc interface to work with WSGI, the HTTP authorization information needs to be passed to the WSGI handler. This is done by setting WSGIPassAuthorization On in the apache2 config file snippet. Ref: http://www.arnebrodowski.de/blog/508-Django,-mod_wsgi-and-HTTP-Authentication.html Signed-off-by: martin f. krafft <madduck@madduck.net> Signed-off-by: Jeremy Kerr <jk@ozlabs.org>
Diffstat (limited to 'patchwork.wsgi')
l---------patchwork.wsgi1
1 files changed, 1 insertions, 0 deletions
diff --git a/patchwork.wsgi b/patchwork.wsgi
new file mode 120000
index 0000000..cf13d18
--- /dev/null
+++ b/patchwork.wsgi
@@ -0,0 +1 @@
+lib/apache2/patchwork.wsgi \ No newline at end of file