1 == Upgrading to 3b8a61c ==
3 Recent commits have changed a few admin-visible components of patchwork, so
4 upgrading to post-commit 3b8a61c involves a few steps:
6 - Update the database schema, by running the 015-add-patch-tags.sql script,
7 and re-run the grants script.
9 For example, on postgres:
11 psql -f lib/sql/migration/015-add-patch-tags.sql patchwork
12 psql -f lib/sql/grant-all.postgres.sql patchwork
14 - Update to the new settings infrastructure. By default, settings are read
15 from patchwork/settings/production.py. To migrate, use the template:
17 cp patchwork/settings/production{.example,}.py
19 and merge your previous settings (from apps/local_settings.py) into
22 - Fixup external references to apps/
24 The apps/ directory is gone; the patchwork module is now in the top-level
25 directory. If you have scripts that run anything from apps/ (eg, incoming
26 mail parsers that call parsemail.sh, and cron scripts), then remove the apps/
29 apps/patchwork/ -> patchwork/
31 (or you can create a symlink - apps/ -> .)
33 - Update any external scripts to use the new settings module
35 If you have been running scripts (eg, from cron) that set the
36 DJANGO_SETTINGS_MODULE environment variable, you'll need to update that
37 to the new settings system. Typically:
39 DJANGO_SETTINGS_MODULE=patchwork.settings.production
41 The manage.py script has been moved from apps/ into the top-level directory
44 - Run the 'collectstatic' management command:
46 ./manage.py collectstatic
48 Ensure that the STATIC_ROOT setting points somewhere sensible (eg, the
49 absolute path of htdocs/static in the patchwork tree).
51 - Update apache to use the new static content.
53 Static content is now in all under STATIC_ROOT, the apache configuration
54 should be simpler now. The core config will be:
56 DocumentRoot /srv/patchwork/htdocs/
57 Alias /static/ /srv/patchwork/htdocs/static/
58 WSGIScriptAlias / /srv/pathchwork/lib/apache2/patchwork.wsgi
59 WSGIPassAuthorization On