3 Patchwork uses the django framework - there is some background on deploying
4 django applications here:
6 http://www.djangobook.com/en/1.0/chapter20/
8 You'll need the following (applications used for patchwork development are
11 * A python interpreter
13 * A webserver (apache)
15 * A database server (postgresql)
19 At present, I've tested with PostgreSQL and (to a lesser extent) MySQL
20 database servers. If you have any (positive or negative) experiences with
23 For the following commands, a $ prefix signifies that the command should be
24 entered at your shell prompt, and a > prefix signifies the commant-line
25 client for your sql server (psql or mysql)
27 Create a database for the system, add accounts for two system users: the
28 web user (the user that your web server runs as) and the mail user (the
29 user that your mail server runs as). On Ubuntu these are
30 www-data and nobody, respectively.
39 > CREATE DATABASE 'patchwork';
40 > INSERT INTO user (Host, User) VALUES ('localhost', 'www-data');
41 > INSERT INTO user (Host, User) VALUES ('localhost', 'nobody');
45 You'll need to customise apps/settings.py to suit your database, and
46 change the SECRET_KEY variable too. While you're there, change the
47 following to suit your installation:
54 Then, get patchwork to create its tables in your configured database:
59 And add privileges for your mail and web users:
62 psql -f lib/sql/grant-all.sql patchwork
67 Example apache configuration files are in lib/apache/.
71 This should be the simpler of the two to set up. An example apache
72 configuration file is in:
74 lib/apache/patchwork.mod_python.conf
76 However, mod_python and mod_php may not work well together. So, if your
77 web server is used for serving php files, the fastcgi method may suit
82 django has built-in support for fastcgi, which requires the
83 'flup' python module. An example configuration is in:
85 lib/apache/patchwork.fastcgi.conf
87 - this also requires the mod_rewrite apache module to be loaded.
89 Once you have apache set up, you can start the fastcgi server with:
91 cd /srv/patchwork/apps
92 ./manage.py runfcgi method=prefork \
93 socket=/srv/patchwork/var/fcgi.sock \
94 pidfile=/srv/patchwork/var/fcgi.pid
96 4. Configure patchwork
97 Now, you should be able to administer patchwork, by visiting the
100 http://your-host/admin/
102 You'll probably want to do the following:
104 * Set up your projects
107 5. Subscribe a local address to the mailing list
109 You will need an email address for patchwork to receive email on - for
110 example - patchwork@, and this address will need to be subscribed to the
111 list. Depending on the mailing list, you will probably need to confirm the
112 subscription - temporarily direct the alias to yourself to do this.
114 6. Setup your MTA to deliver mail to the parsemail script
116 Your MTA will need to deliver mail to the parsemail script in the email/
117 directory. (Note, do not use the parsemail.py script directly). Something
118 like this in /etc/aliases is suitable for postfix:
120 patchwork: "|/srv/patchwork/apps/patchwork/bin/parsemail.sh"
122 You may need to customise the parsemail.sh script if you haven't installed
123 patchwork in /srv/patchwork.
125 Test that you can deliver a patch to this script:
127 sudo -u nobody /srv/patchwork/apps/patchwork/bin/parsemail.sh < mail
132 * __init__() got an unexpected keyword argument 'max_length'
134 - you're running an old version of django. If your distribution doesn't
135 provide a newer version, just download and extract django into
138 * ERROR: permission denied for relation patchwork_...
140 - the user that patchwork is running as (ie, the user of the web-server)
141 doesn't have access to the patchwork tables in the database. Check that
142 your web-server user exists in the database, and that it has permissions