Verbatim:Deployment: Difference between revisions
Jump to navigation
Jump to search
(partial update for Pootle 1.3 (work in progress)) |
No edit summary |
||
Line 13: | Line 13: | ||
== Setup == | == Setup == | ||
I've added some scripts etc. to [https://gist.github.com/cb33a48c6945db24f13a github]. | |||
As the apache user, pick a dir where you want to deploy Pootle (pootle_dir), then: | As the apache user, pick a dir where you want to deploy Pootle (pootle_dir), then: | ||
* cd pootle_dir | * <code>cd pootle_dir</code> | ||
* virtualenv pootle_env | * <code>virtualenv pootle_env</code> | ||
* ... | * <code>cd pootle_env/bin</code> | ||
* <code>. activate</code> | |||
* <code>wget .../modpython_wrapper.py</code> (from github); chmod +x it | |||
== Configuration == | == Configuration == |
Revision as of 10:26, 4 November 2009
Verbatim » Deployment
Pre-Deployment Checklist
- Prerequisites
- Python >= 2.4
- (list of dependencies)
- Some of these probably exist as RPMs, but they can also just be installed into the virtualenv
- python-lxml
- python-sqlite2
- python-ldap
- At least gettext version 0.15. This seems to upgrade cleanly in Redhat with no dependency issues (bug 438706)
- At least SVN 1.5 (we make use of --with-revprop)
Setup
I've added some scripts etc. to github.
As the apache user, pick a dir where you want to deploy Pootle (pootle_dir), then:
cd pootle_dir
virtualenv pootle_env
cd pootle_env/bin
. activate
wget .../modpython_wrapper.py
(from github); chmod +x it
Configuration
- more details on these steps but a summary:
- Create a Verbatim SSH account on the SVN server using an SSH key with no passphrase
- Copy the key to a .ssh directory in the home directory of the verbatim user on the verbatim server
- Add commit hooks to the SVN server for translate:author
- checkout https://translate.svn.sourceforge.net/svnroot/translate/src/branches/mozootle
- Copy pootle.prefs to a configuration directory and configure it
- The command to run the server is ./PootleServer --prefsfile=/path/to/pootle.prefs --port=80
- note: the pootle tree must be owned by whatever user is running the pootle server
Post-deployment Checklist
todo: verification things are working, cron jobs, nagios checks, etc.