1136: Support for apache/mod_wsgi

plae****@gmai***** (Google Code) (Is this you? Claim this profile.)
June 14, 2010 
This was required to get review-board running with mod_wsgi under apache

reviewboard.wsgi::

#!/usr/bin/env python
import os, sys

sys.path.insert(0, "path/to/conf")
os.environ["DJANGO_SETTINGS_MODULE"] = "reviewboard.settings"
os.environ["PYTHON_EGG_CACHE"] = "path/to/egg_cache"

import django.core.handlers.wsgi
_application = django.core.handlers.wsgi.WSGIHandler()

def application(environ, start_response):
    environ['PATH_INFO'] = environ['SCRIPT_NAME'] + environ['PATH_INFO']
    return _application(environ, start_response)
#1 plae****@gmai***** (Google Code) (Is this you? Claim this profile.) 
And for apache conf:

# Reviewboard
Alias /media "path/to/media"
Alias /errordocs "path/to/errordocs"
WSGIScriptAlias /path-to-review-board /path/to/reviewboard.wsgi
chipx86
#2 chipx86
  • +Confirmed
  • +Milestone-Release1.1
    +Component-Deployment
#3 Graham.D********@gmai***** (Google Code) (Is this you? Claim this profile.) 
That WSGI script file is only correct if using Django < 1.0 and the application is mounted at a sub URL and the 
urls.py is setup in a specific way. If the application is mounted at the root of the site, it would be done 
differently and you wouldn't need the fiddles at all if using Django 1.0 or later.

Thus, you are going to need a lot of qualifications on this if you are going to promote it as the deployment 
method.
chipx86
#4 chipx86
  • +Milestone-Release1.5
david
#5 david 
Fixed in 9fe599c. Thanks!
  • -Confirmed
    +Fixed
#6 julian*******@gmai***** (Google Code) (Is this you? Claim this profile.) 
For the record, I think the revisions this was fixed in really were

http://github.com/reviewboard/reviewboard/commit/e4aa4ff94fef7745fc1e137575e9ebe6b61fa88d
http://github.com/reviewboard/reviewboard/commit/c4355f102f7a5766f45c54245670a0009df8f660