X-Git-Url: https://git.ozlabs.org/?a=blobdiff_plain;f=docs%2FINSTALL;h=5716ed231b59ac36dc6e4e3f68ad17e3011cb67e;hb=f49c72da5545f2da49dd83d9ec54fe232cf60360;hp=050fc9f10a4cefcef22454967d2d234ee3326d30;hpb=017f73b059aadfce30ee29d2aceeab92739105a6;p=patchwork diff --git a/docs/INSTALL b/docs/INSTALL index 050fc9f..5716ed2 100644 --- a/docs/INSTALL +++ b/docs/INSTALL @@ -3,16 +3,17 @@ Deploying Patchwork Patchwork uses the django framework - there is some background on deploying django applications here: - http://www.djangobook.com/en/1.0/chapter20/ + http://www.djangobook.com/en/2.0/chapter12/ You'll need the following (applications used for patchwork development are in brackets): * A python interpreter - * django + * django >= 1.5 * A webserver (apache) * mod_python or flup - * A database server (postgresql) + * A database server (postgresql, mysql) + * relevant python modules for the database server (e.g: python-mysqldb) 1. Database setup @@ -64,6 +65,17 @@ in brackets): > CREATE USER 'www-data'@'localhost' IDENTIFIED BY ''; > CREATE USER 'nobody'@'localhost' IDENTIFIED BY ''; + Once that is done, you need to tell Django about the new Database + settings, using local_settings.py (see below) to override the defaults + in settings.py: + + DATABASE_ENGINE = 'mysql' + DATABASE_NAME = 'patchwork' + DATABASE_USER = 'root' + DATABASE_PASSWORD = 'my_secret_root_password' + DATABSE_HOST = 'localhost' + DATABASE_PORT = '' + 2. Django setup Set up some initial directories in the patchwork base directory: @@ -73,26 +85,14 @@ in brackets): lib/packages is for stuff we'll download, lib/python is to add to our python path. We'll symlink python modules into lib/python. - At the time of release, patchwork depends on django version 1.0 or + At the time of release, patchwork depends on django version 1.5 or later. Your distro probably provides this. If not, do a: cd lib/packages - svn checkout http://code.djangoproject.com/svn/django/tags/releases/1.2 + git clone https://github.com/django/django.git -b stable/1.5.x cd ../python ln -s ../packages/django/django ./django - We also use some Javascript libraries: - - cd lib/packages - mkdir jquery - cd jquery - wget http://jqueryjs.googlecode.com/files/jquery-1.3.min.js - wget http://www.isocra.com/articles/jquery.tablednd_0_5.js.zip - unzip jquery.tablednd_0_5.js.zip jquery.tablednd_0_5.js - cd ../../../htdocs/js/ - ln -s ../../lib/packages/jquery/jquery-1.3.min.js ./ - ln -s ../../lib/packages/jquery/jquery.tablednd_0_5.js ./ - The settings.py file contains default settings for patchwork, you'll need to configure settings for your own setup. @@ -113,12 +113,6 @@ in brackets): chars = string.letters + string.digits + string.punctuation print repr("".join([random.choice(chars) for i in range(0,50)])) - If you have patchwork installed in somewhere other than /srv/patchwork, - you'll also need to define: - - MEDIA_ROOT - TEMPLATE_DIRS - If you wish to enable the XML-RPC interface, add the following to your local_settings.py file: @@ -216,6 +210,39 @@ fastcgi: sudo -u nobody /srv/patchwork/apps/patchwork/bin/parsemail.sh < mail +7. Set up the patchwork cron script + + Patchwork uses a cron script to clean up expired registrations, and + send notifications of patch changes (for projects with this enabled). + + Something like this in your crontab should work: + + # m h dom mon dow command + PYTHONPATH=apps:. + DJANGO_SETTINGS_MODULE=settings + */10 * * * * cd patchwork; python apps/patchwork/bin/patchwork-cron.py + + + - the frequency should be the same as the NOTIFICATION_DELAY_MINUTES + setting, which defaults to 10 minutes. + +8. Optional: Configure your VCS to automatically update patches + + The tools directory of the patchwork distribution contains a file + named post-receive.hook which is an example git hook that can be + used to automatically update patches to the Accepted state when + corresponding comits are pushed via git. + + To install this hook, simply copy it to the .git/hooks directory on + your server, name it post-receive, and make it executable. + + This sample hook has support to update patches to different states + depending on which branch is being pushed to. See the STATE_MAP + setting in that file. + + If you are using a system other than git, you can likely write a + similar hook using pwclient to update patch state. If you do write + one, please contribute it. Some errors: