clandmeter/patchwork/lib/apache2, branch master

Update documentation and default settings to suit patchwork deployment model

2015-05-28T01:05:37+00:00

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

lib/apache2: Update sample configuration files for new staticfiles application

2015-05-27T02:26:41+00:00

The static files app will collect all of the static files into
STATIC_ROOT, which is under htdocs/static/.

Signed-off-by: Jeremy Kerr

lib/apache2: use django-1.7-compatible wsgi application

2015-05-27T02:26:41+00:00

Signed-off-by: Jeremy Kerr

Move to a more recent django project structure

2015-05-27T02:26:41+00:00

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

Update manage.py to post a post-1.4 version.

2014-04-22T12:13:23+00:00

Django version 1.6 deprecates some of the django.core.management API, so
we need a post-1.4 version.

The semantics with app include paths have changed with this version, so
update the urlconf to use the same path as manage.py.

Signed-off-by: Jeremy Kerr

helpers: Change patchwork.wsgi to include the apps/ dir in sys.path

2011-02-28T01:54:15+00:00

Without this, templates will crash as they reference patchwork.
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 
Signed-off-by: Jeremy Kerr

lib/apache2: Add WSGI Handler

2010-08-10T03:49:35+00:00

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 
Signed-off-by: Jeremy Kerr

Pass Authorization headers in fastcgi application

2008-09-09T03:11:12+00:00

By default, mod_fcgi doens't allow the Authorization header, so
enable -pass-header, and handle the different header name in the
xmlrpc view

Signed-off-by: Jeremy Kerr

mod_python example configuration fixes

2008-09-08T00:03:48+00:00

These fixes correct the example patchwork.mod_python.conf file to
actually work properly:

* Patchwork base directory needs to be in PythonPath so that
  things like "apps.urls" will import

* Set DJANGO_SETTINGS_MODULE to "settings" instead of
  "patchwork.settings" so that it can find the settings file to
  import

* Use LocationMatch instead of Location in order for the pattern
  matching to work (this was causing none of the images/stylesheets
  to be found when using mod_python)

Signed-off-by: Nate Case 
Signed-off-by: Jeremy Kerr

Inital commit

2008-08-21T01:38:06+00:00

Signed-off-by: Jeremy Kerr