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)
20 At present, I've tested with PostgreSQL and (to a lesser extent) MySQL
21 database servers. If you have any (positive or negative) experiences with
24 For the following commands, a $ prefix signifies that the command should be
25 entered at your shell prompt, and a > prefix signifies the commant-line
26 client for your sql server (psql or mysql)
28 Create a database for the system, add accounts for two system users: the
29 web user (the user that your web server runs as) and the mail user (the
30 user that your mail server runs as). On Ubuntu these are
31 www-data and nobody, respectively.
33 As an alternative, you can use password-based login and a single database
34 account. This is described further down.
36 For PostgreSQL (ident-based)
42 - postgres uses the standard UNIX authentication, so these users
43 will only be accessible for processes running as the same username.
44 This means that no passwords need to be set.
46 For PostgreSQL (password-based)
48 $ createuser -PE patchwork
49 $ createdb -O patchwork patchwork
51 Once that is done, you need to tell Django about the new Database
52 settings, using local_settings.py (see below) to override the defaults
57 'ENGINE': 'django.db.backends.postgresql_psycopg2',
61 'PASSWORD': 'my_secret_password',
68 > CREATE DATABASE 'patchwork';
69 > CREATE USER 'www-data'@'localhost' IDENTIFIED BY '<password>';
70 > CREATE USER 'nobody'@'localhost' IDENTIFIED BY '<password>';
72 Once that is done, you need to tell Django about the new Database
73 settings, using local_settings.py (see below) to override the defaults
78 'ENGINE': 'django.db.backends.mysql',
82 'PASSWORD': 'my_secret_password',
89 Set up some initial directories in the patchwork base directory:
91 mkdir -p lib/packages lib/python
93 lib/packages is for stuff we'll download, lib/python is to add
94 to our python path. We'll symlink python modules into lib/python.
96 At the time of release, patchwork depends on django version 1.5 or
97 later. Your distro probably provides this. If not, do a:
100 git clone https://github.com/django/django.git -b stable/1.5.x
102 ln -s ../packages/django/django ./django
104 The settings.py file contains default settings for patchwork, you'll
105 need to configure settings for your own setup.
107 Rather than edit settings.py, create a file 'local_settings.py', and
108 override or add settings as necessary. You'll need to define the
116 NOTIFICATION_FROM_EMAIL
118 You can generate the SECRET_KEY with the following python code:
120 import string, random
121 chars = string.letters + string.digits + string.punctuation
122 print repr("".join([random.choice(chars) for i in range(0,50)]))
124 If you wish to enable the XML-RPC interface, add the following to
125 your local_settings.py file:
129 Then, get patchwork to create its tables in your configured database:
132 PYTHONPATH=../lib/python ./manage.py syncdb
134 And add privileges for your mail and web users. This is only needed if
135 you use the ident-based approach. If you use password-based database
136 authentication, you can skip this step.
139 psql -f lib/sql/grant-all.postgres.sql patchwork
142 mysql patchwork < lib/sql/grant-all.mysql.sql
147 Example apache configuration files are in lib/apache2/.
150 django has built-in support for WSGI, which supersedes the fastcgi
151 handler. It is thus the preferred method to run patchwork.
153 The necessary configuration for Apache2 may be found in
155 lib/apache2/patchwork.wsgi.conf.
157 You will need to install/enable mod_wsgi for this to work:
164 An example apache configuration file for mod_python is in:
166 lib/apache2/patchwork.mod_python.conf
168 However, mod_python and mod_php may not work well together. So, if your
169 web server is used for serving php files, the fastcgi method may suit
174 django has built-in support for fastcgi, which requires the
175 'flup' python module. An example configuration is in:
177 lib/apache2/patchwork.fastcgi.conf
179 - this also requires the mod_rewrite apache module to be loaded.
181 Once you have apache set up, you can start the fastcgi server with:
183 cd /srv/patchwork/apps
184 ./manage.py runfcgi method=prefork \
185 socket=/srv/patchwork/var/fcgi.sock \
186 pidfile=/srv/patchwork/var/fcgi.pid
188 4. Configure patchwork
189 Now, you should be able to administer patchwork, by visiting the
192 http://your-host/admin/
194 You'll probably want to do the following:
196 * Set up your projects
197 * Configure your website address (in the Sites) section of the admin
199 5. Subscribe a local address to the mailing list
201 You will need an email address for patchwork to receive email on - for
202 example - patchwork@, and this address will need to be subscribed to the
203 list. Depending on the mailing list, you will probably need to confirm the
204 subscription - temporarily direct the alias to yourself to do this.
206 6. Setup your MTA to deliver mail to the parsemail script
208 Your MTA will need to deliver mail to the parsemail script in the email/
209 directory. (Note, do not use the parsemail.py script directly). Something
210 like this in /etc/aliases is suitable for postfix:
212 patchwork: "|/srv/patchwork/apps/patchwork/bin/parsemail.sh"
214 You may need to customise the parsemail.sh script if you haven't installed
215 patchwork in /srv/patchwork.
217 Test that you can deliver a patch to this script:
219 sudo -u nobody /srv/patchwork/apps/patchwork/bin/parsemail.sh < mail
221 7. Set up the patchwork cron script
223 Patchwork uses a cron script to clean up expired registrations, and
224 send notifications of patch changes (for projects with this enabled).
226 Something like this in your crontab should work:
228 # m h dom mon dow command
230 DJANGO_SETTINGS_MODULE=settings
231 */10 * * * * cd patchwork; python apps/patchwork/bin/patchwork-cron.py
234 - the frequency should be the same as the NOTIFICATION_DELAY_MINUTES
235 setting, which defaults to 10 minutes.
237 8. Optional: Configure your VCS to automatically update patches
239 The tools directory of the patchwork distribution contains a file
240 named post-receive.hook which is an example git hook that can be
241 used to automatically update patches to the Accepted state when
242 corresponding comits are pushed via git.
244 To install this hook, simply copy it to the .git/hooks directory on
245 your server, name it post-receive, and make it executable.
247 This sample hook has support to update patches to different states
248 depending on which branch is being pushed to. See the STATE_MAP
249 setting in that file.
251 If you are using a system other than git, you can likely write a
252 similar hook using pwclient to update patch state. If you do write
253 one, please contribute it.
257 * __init__() got an unexpected keyword argument 'max_length'
259 - you're running an old version of django. If your distribution doesn't
260 provide a newer version, just download and extract django into
263 * ERROR: permission denied for relation patchwork_...
265 - the user that patchwork is running as (ie, the user of the web-server)
266 doesn't have access to the patchwork tables in the database. Check that
267 your web-server user exists in the database, and that it has permissions
270 * pwclient fails for actions that require authentication, but a username
271 and password is given int ~/.pwclient rc. Server reports "No authentication
274 - if you're using the FastCGI interface to apache, you'll need the
275 '-pass-header Authorization' option to the FastCGIExternalServer
276 configuration directive.