patchwork - Unnamed repository; edit this file 'description' to name the repository.

	Commit message (Collapse)	Author	Age
*	wsgi: Move wsgi file to expected location	Stephen Finucane	2016-02-08
\| \| \| \| \| \| \| \|	Django places a wsgi.py file in the root of each application's directory. Do this, adding a symlink to preserve existing operation for users. Signed-off-by: Stephen Finucane <stephen.finucane@intel.com>
*	Update documentation and default settings to suit patchwork deployment model	Jeremy Kerr	2015-05-28
\| \| \| \| \| \| \| \| \| \| \| \|	We've always allowed configuration without altering any of the version-controlled files. With the recent settings changes, we have an extra level of indirection with the dev/prod settings modules. Since we have to edit a config file anyway, this change moves the prod.py settings file to a template, which is then used directly by mange.py (and the wsgi application). Signed-off-by: Jeremy Kerr <jk@ozlabs.org>
*	lib/apache2: use django-1.7-compatible wsgi application	Jeremy Kerr	2015-05-27
\| \| \| \|	Signed-off-by: Jeremy Kerr <jk@ozlabs.org>
*	Move to a more recent django project structure	Jeremy Kerr	2015-05-27
\| \| \| \| \| \| \| \| \| \|	This change updates patchwor to the newer project struture: we've moved the actual application out of the apps/ directory, and the patchwork-specific templates to under the patchwork application. This gives us the manage.py script in the top-level now. Signed-off-by: Jeremy Kerr <jk@ozlabs.org>
*	helpers: Change patchwork.wsgi to include the apps/ dir in sys.path	Guilherme Salgado	2011-02-28
\| \| \| \| \| \| \| \| \| \| \|	Without this, templates will crash as they reference patchwork.<module> directly. Also removes the patchwork.wsgi symlink from the root and use the real file in patchwork.wsgi.conf instead, as suggested by Dirk Wallenstein. Signed-off-by: Guilherme Salgado <guilherme.salgado@linaro.org> Signed-off-by: Jeremy Kerr <jk@ozlabs.org>
*	lib/apache2: Add WSGI Handler	Martin Krafft	2010-08-10
	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>