3 Patchwork uses the django framework - there is some background on deploying
4 django applications here:
6 http://www.djangobook.com/en/2.0/chapter12/
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, mysql)
16 * relevant python modules for the database server (e.g: python-mysqldb)
21 At present, I've tested with PostgreSQL and (to a lesser extent) MySQL
22 database servers. If you have any (positive or negative) experiences with
25 For the following commands, a $ prefix signifies that the command should be
26 entered at your shell prompt, and a > prefix signifies the command-line
27 client for your sql server (psql or mysql)
29 Create a database for the system, add accounts for two system users: the
30 web user (the user that your web server runs as) and the mail user (the
31 user that your mail server runs as). On Ubuntu these are
32 www-data and nobody, respectively.
34 As an alternative, you can use password-based login and a single database
35 account. This is described further down.
37 For PostgreSQL (ident-based)
43 - postgres uses the standard UNIX authentication, so these users
44 will only be accessible for processes running as the same username.
45 This means that no passwords need to be set.
47 For PostgreSQL (password-based)
49 $ createuser -PE patchwork
50 $ createdb -O patchwork patchwork
52 Once that is done, you need to tell Django about the new Database
53 settings, using local_settings.py (see below) to override the defaults
58 'ENGINE': 'django.db.backends.postgresql_psycopg2',
62 'PASSWORD': 'my_secret_password',
69 > CREATE DATABASE patchwork CHARACTER SET utf8;
70 > CREATE USER 'www-data'@'localhost' IDENTIFIED BY '<password>';
71 > CREATE USER 'nobody'@'localhost' IDENTIFIED BY '<password>';
73 Once that is done, you need to tell Django about the new Database
74 settings, using local_settings.py (see below) to override the defaults
79 'ENGINE': 'django.db.backends.mysql',
83 'PASSWORD': 'my_secret_password',
85 'TEST_CHARSET': 'utf8',
89 TEST_CHARSET is used when creating tables for the test suite. Without
90 it, tests checking for the correct handling of non-ASCII characters
96 Set up some initial directories in the patchwork base directory:
98 mkdir -p lib/packages lib/python
100 lib/packages is for stuff we'll download; lib/python is to add
101 to our python path. We'll symlink python modules into lib/python.
103 At the time of release, patchwork depends on django version 1.5 or
104 later. Your distro probably provides this. If not, do a:
107 git clone https://github.com/django/django.git -b stable/1.5.x
109 ln -s ../packages/django/django ./django
111 The patchwork/settings/*.py files contain default settings for patchwork,
112 you'll need to configure settings for your own setup.
114 Rather than editing these files (which will cause conflicts when you
115 update the base patchwork code), create a file 'production.py', based on
118 cp patchwork/settings/production.example.py \
119 patchwork/settings/production.py
121 and override or add settings as necessary. You'll need to define the
130 NOTIFICATION_FROM_EMAIL
132 You can generate the SECRET_KEY with the following python code:
134 import string, random
135 chars = string.letters + string.digits + string.punctuation
136 print repr("".join([random.choice(chars) for i in range(0,50)]))
138 If you wish to enable the XML-RPC interface, add the following to
139 your local_settings.py file:
143 Then, get patchwork to create its tables in your configured database:
145 PYTHONPATH=lib/python ./manage.py syncdb
147 And add privileges for your mail and web users. This is only needed if
148 you use the ident-based approach. If you use password-based database
149 authentication, you can skip this step.
152 psql -f lib/sql/grant-all.postgres.sql patchwork
155 mysql patchwork < lib/sql/grant-all.mysql.sql
160 Example apache configuration files are in lib/apache2/.
164 django has built-in support for WSGI, which supersedes the fastcgi
165 handler. It is thus the preferred method to run patchwork.
167 The necessary configuration for Apache2 may be found in
169 lib/apache2/patchwork.wsgi.conf.
171 You will need to install/enable mod_wsgi for this to work:
179 An example apache configuration file for mod_python is in:
181 lib/apache2/patchwork.mod_python.conf
183 However, mod_python and mod_php may not work well together. So, if your
184 web server is used for serving php files, the fastcgi method may suit
190 django has built-in support for fastcgi, which requires the
191 'flup' python module. An example configuration is in:
193 lib/apache2/patchwork.fastcgi.conf
195 - this also requires the mod_rewrite apache module to be loaded.
197 Once you have apache set up, you can start the fastcgi server with:
200 ./manage.py runfcgi method=prefork \
201 socket=/srv/patchwork/var/fcgi.sock \
202 pidfile=/srv/patchwork/var/fcgi.pid
205 4. Configure patchwork
206 Now, you should be able to administer patchwork, by visiting the
209 http://your-host/admin/
211 You'll probably want to do the following:
213 * Set up your projects
214 * Configure your website address (in the Sites) section
217 5. Subscribe a local address to the mailing list
219 You will need an email address for patchwork to receive email on - for
220 example - patchwork@, and this address will need to be subscribed to the
221 list. Depending on the mailing list, you will probably need to confirm the
222 subscription - temporarily direct the alias to yourself to do this.
225 6. Setup your MTA to deliver mail to the parsemail script
227 Your MTA will need to deliver mail to the parsemail script in the email/
228 directory. (Note, do not use the parsemail.py script directly). Something
229 like this in /etc/aliases is suitable for postfix:
231 patchwork: "|/srv/patchwork/patchwork/bin/parsemail.sh"
233 You may need to customise the parsemail.sh script if you haven't installed
234 patchwork in /srv/patchwork.
236 Test that you can deliver a patch to this script:
238 sudo -u nobody /srv/patchwork/patchwork/bin/parsemail.sh < mail
241 7. Set up the patchwork cron script
243 Patchwork uses a cron script to clean up expired registrations, and
244 send notifications of patch changes (for projects with this enabled).
246 Something like this in your crontab should work:
248 # m h dom mon dow command
250 DJANGO_SETTINGS_MODULE=patchwork.settings.production
251 */10 * * * * cd patchwork; python patchwork/bin/patchwork-cron.py
254 - the frequency should be the same as the NOTIFICATION_DELAY_MINUTES
255 setting, which defaults to 10 minutes.
258 8. Optional: Configure your VCS to automatically update patches
260 The tools directory of the patchwork distribution contains a file
261 named post-receive.hook which is an example git hook that can be
262 used to automatically update patches to the Accepted state when
263 corresponding comits are pushed via git.
265 To install this hook, simply copy it to the .git/hooks directory on
266 your server, name it post-receive, and make it executable.
268 This sample hook has support to update patches to different states
269 depending on which branch is being pushed to. See the STATE_MAP
270 setting in that file.
272 If you are using a system other than git, you can likely write a
273 similar hook using pwclient to update patch state. If you do write
274 one, please contribute it.
279 * __init__() got an unexpected keyword argument 'max_length'
281 - you're running an old version of django. If your distribution doesn't
282 provide a newer version, just download and extract django into
285 * ERROR: permission denied for relation patchwork_...
287 - the user that patchwork is running as (ie, the user of the web-server)
288 doesn't have access to the patchwork tables in the database. Check that
289 your web-server user exists in the database, and that it has permissions
292 * pwclient fails for actions that require authentication, but a username
293 and password is given in ~/.pwclientrc. Server reports "No authentication
296 - if you're using the FastCGI interface to apache, you'll need the
297 '-pass-header Authorization' option to the FastCGIExternalServer
298 configuration directive.