View source for Verbatim:Deployment

[[Verbatim]] &raquo; Deployment

NOTE:  This page contains notes about Mozilla's installation of Pootle.  If you wish to install Pootle, the best would be to consult the [http://translate.sourceforge.net/wiki/pootle/index documentation of the Pootle project].

== Pre-Deployment Checklist ==
* Prerequisites
** Python >= 2.4
** [http://pip.openplans.org/ pip]
** python-sqlite2
** python-ldap
** MySQL-python
** At least gettext version 0.15.  This seems to upgrade cleanly in Redhat with no dependency issues ([https://bugzilla.mozilla.org/show_bug.cgi?id=438706 bug 438706])
** At least SVN 1.5 (we make use of <code>--with-revprop</code>)
** libxml2-devel
** libxslt-devel
** python-devel

([http://translate.sourceforge.net/wiki/pootle/installation list of Pootle's dependencies])

== 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:

* Create and activate a virtualenv
** <code>cd pootle_dir</code>
** <code>virtualenv pootle_env</code>
** <code>. pootle_env/bin/activate</code>
* Install all required packages using <code>pip</code>
** <code>wget .../requirements.txt</code> (from github)
** <code>pip -E pootle_env install -r requirements.txt</code>
* Download and extract Pootle itself (from the [http://sourceforge.net/projects/translate/files/Pootle/ SourceForge releases]) so that it lives under pootle_dir/Pootle

Set up Apache and mod_python to properly run Pootle
* <code>cd pootle_env/bin</code>
* <code>wget .../modpython_wrapper.py</code> (from github); chmod +x it
* set up Apache config similarly to the <code>apache-host.conf</code> on github; important parts:
** <code>PythonHandler modpython_wrapper</code> refers to the .py file we put into <code>pootle_dir/pootle_env</code> above.
** make sure to adjust pootle_dir appropriately in all places
** the config should in the end use HTTPS and forward HTTP->HTTPS, because we use LDAP auth

== Configuration ==
* set up SVN user ([http://micropipes.com/blog/2008/09/19/committing-to-svn-securely-from-a-web-application/ more details on these steps] but here's 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
* check out inital projects into <code>Pootle/po/(project-slug)</code>, for example:
# <code>cd pootle_dir/Pootle/po</code>
# <code>svn co svn+ssh://svn.mozilla.org/addons/trunk/site/app/locale amo</code>
* set up Pootle itself
# create a MySQL db and user
# set up a memcached instance for Pootle
# edit <code>Pootle/localconfig.py</code>, there:
# change <code>DATABASE_*</code>
# switch <code>AUTHENTICATION_BACKENDS</code> to use LDAP, and adjust the credentials/settings there
# switch <code>CACHE_BACKEND</code> with the memcached option
* initialize Pootle
# in <code>pootle_dir/Pootle</code>, run the database initialization steps, including creation of a first admin user:
# <code>./manage.py syncdb</code>
# <code>./manage.py initdb</code>
# <code>./manage.py refresh_stats</code>

== Post-deployment Checklist ==
* make sure at the very least <code>/po</code> and <code>/dbs</code> are owned and writeable by the apache user, probably <code>pootle/settings.py</code> too.
* once it all works, switch <code>DEBUG</code> in <code>localconfig.py</code> to'' False''
''todo: verification things are working, cron jobs, nagios checks, etc.''

You might also want to look into tips for [http://translate.sourceforge.net/wiki/pootle/optimisation Pootle optimisation]].