summaryrefslogtreecommitdiff
path: root/docs
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 /docs
parentcb407f1dddee250eee5664f163868e96ada292c9 (diff)
downloadpatchwork-d636cb34a3b13ea3e6b776e951e6276a94d968c6.tar
patchwork-d636cb34a3b13ea3e6b776e951e6276a94d968c6.tar.gz
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 'docs')
-rw-r--r--docs/INSTALL14
1 files changed, 10 insertions, 4 deletions
diff --git a/docs/INSTALL b/docs/INSTALL
index fdee592..7e1f309 100644
--- a/docs/INSTALL
+++ b/docs/INSTALL
@@ -108,11 +108,17 @@ in brackets):
cd ../python
ln -s ../packages/django/django ./django
- The settings.py file contains default settings for patchwork, you'll
- need to configure settings for your own setup.
+ The patchwork/settings/*.py files contain default settings for patchwork,
+ you'll need to configure settings for your own setup.
- Rather than edit settings.py, create a file 'local_settings.py', and
- override or add settings as necessary. You'll need to define the
+ Rather than editing these files (which will cause conflicts when you
+ update the base patchwork code), create a file 'production.py', based on
+ the example:
+
+ cp patchwork/settings/production.example.py \
+ patchwork/settings/production.py
+
+ and override or add settings as necessary. You'll need to define the
following:
SECRET_KEY