1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
|
Deploying Patchwork
Patchwork uses the django framework - there is some background on deploying
django applications here:
http://www.djangobook.com/en/1.0/chapter20/
You'll need the following (applications used for patchwork development are
in brackets):
* A python interpreter
* djano
* A webserver (apache)
* mod_python or flup
* A database server (postgresql)
1. Database setup
At present, I've tested with PostgreSQL and (to a lesser extent) MySQL
database servers. If you have any (positive or negative) experiences with
either, email me.
For the following commands, a $ prefix signifies that the command should be
entered at your shell prompt, and a > prefix signifies the commant-line
client for your sql server (psql or mysql)
Create a database for the system, add accounts for two system users: the
web user (the user that your web server runs as) and the mail user (the
user that your mail server runs as). On Ubuntu these are
www-data and nobody, respectively.
PostgreSQL:
createdb patchwork
createuser www-data
createuser nobody
MySQL:
$ mysql
> CREATE DATABASE 'patchwork';
> INSERT INTO user (Host, User) VALUES ('localhost', 'www-data');
> INSERT INTO user (Host, User) VALUES ('localhost', 'nobody');
2. Django setup
At the time of initial release, patchwork depends on a svn version of
django. I've been using svn commit 7854 - but anything after this
point should be fine. If your distribution provides a sufficiently
recent version of django, you can use that; if not, do a:
cd lib/python
svn checkout http://code.djangoproject.com/svn/django/trunk .
You'll need to customise apps/settings.py to suit your database, and
change the SECRET_KEY variable too. While you're there, change the
following to suit your installation:
SECRET_KEY
ADMINS,
TIME_ZONE
LANGUAGE_CODE
MEDIA_ROOT
You can generate the SECRET_KEY with the following python code:
import string, random
chars = string.letters + string.digits + string.punctuation
print repr("".join([random.choice(chars) for i in range(0,50)]))
Then, get patchwork to create its tables in your configured database:
cd apps/
./manage.py syncdb
And add privileges for your mail and web users:
Postgresql:
psql -f lib/sql/grant-all.sql patchwork
3. Apache setup
Example apache configuration files are in lib/apache/.
mod_python:
This should be the simpler of the two to set up. An example apache
configuration file is in:
lib/apache/patchwork.mod_python.conf
However, mod_python and mod_php may not work well together. So, if your
web server is used for serving php files, the fastcgi method may suit
instead.
fastcgi:
django has built-in support for fastcgi, which requires the
'flup' python module. An example configuration is in:
lib/apache/patchwork.fastcgi.conf
- this also requires the mod_rewrite apache module to be loaded.
Once you have apache set up, you can start the fastcgi server with:
cd /srv/patchwork/apps
./manage.py runfcgi method=prefork \
socket=/srv/patchwork/var/fcgi.sock \
pidfile=/srv/patchwork/var/fcgi.pid
4. Configure patchwork
Now, you should be able to administer patchwork, by visiting the
URL:
http://your-host/admin/
You'll probably want to do the following:
* Set up your projects
* Configure your website address (in the Sites) section of the admin
5. Subscribe a local address to the mailing list
You will need an email address for patchwork to receive email on - for
example - patchwork@, and this address will need to be subscribed to the
list. Depending on the mailing list, you will probably need to confirm the
subscription - temporarily direct the alias to yourself to do this.
6. Setup your MTA to deliver mail to the parsemail script
Your MTA will need to deliver mail to the parsemail script in the email/
directory. (Note, do not use the parsemail.py script directly). Something
like this in /etc/aliases is suitable for postfix:
patchwork: "|/srv/patchwork/apps/patchwork/bin/parsemail.sh"
You may need to customise the parsemail.sh script if you haven't installed
patchwork in /srv/patchwork.
Test that you can deliver a patch to this script:
sudo -u nobody /srv/patchwork/apps/patchwork/bin/parsemail.sh < mail
Some errors:
* __init__() got an unexpected keyword argument 'max_length'
- you're running an old version of django. If your distribution doesn't
provide a newer version, just download and extract django into
lib/python/django
* ERROR: permission denied for relation patchwork_...
- the user that patchwork is running as (ie, the user of the web-server)
doesn't have access to the patchwork tables in the database. Check that
your web-server user exists in the database, and that it has permissions
to the tables.
|
