summaryrefslogtreecommitdiffstats
path: root/manage.py
diff options
context:
space:
mode:
authorJeremy Kerr <jk@ozlabs.org>2015-05-24 17:50:33 +0800
committerJeremy Kerr <jk@ozlabs.org>2015-05-28 09:05:37 +0800
commitd636cb34a3b13ea3e6b776e951e6276a94d968c6 (patch)
tree4be54afc3e1a27af17f1e171f57768a0ec4dccba /manage.py
parentcb407f1dddee250eee5664f163868e96ada292c9 (diff)
downloadpatchwork-d636cb34a3b13ea3e6b776e951e6276a94d968c6.tar.bz2
patchwork-d636cb34a3b13ea3e6b776e951e6276a94d968c6.tar.xz
Update documentation and default settings to suit patchwork deployment model
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>
Diffstat (limited to 'manage.py')
-rwxr-xr-xmanage.py3
1 files changed, 2 insertions, 1 deletions
diff --git a/manage.py b/manage.py
index 04eac77..fe6189e 100755
--- a/manage.py
+++ b/manage.py
@@ -3,7 +3,8 @@ import os
import sys
if __name__ == "__main__":
- os.environ.setdefault("DJANGO_SETTINGS_MODULE", "patchwork.settings.prod")
+ os.environ.setdefault("DJANGO_SETTINGS_MODULE",
+ "patchwork.settings.production")
from django.core.management import execute_from_command_line