Uncategorized

We’re going to install a Production Server configuration of Pootle the ‘Community localization server’ onto a base install of Ubuntu 12.04.3. As part of the base install, you need to have selected the LAMP package option so that MySQL database server installed.

Initial Configuration

Firstly, since we’re going to be doing a lot of package installation, it’s best to move into SuperUser mode:

$ sudo -s

Now let’s start installing all the packages we’re going to need:

root$ apt-get install python-dev libxml2-dev libxslt1-dev

We need Aeidon to support subtitle formats, Levenshtein for speed-up when updating against templates, Xapian for fast text indeing and Zip to provide fast (un)compression of file archives:

CREATE DATABASE pootle CHARACTER SET = ‘utf8′;GRANT ALL PRIVILEGES ON pootle.* TO pootle@localhost IDENTIFIED BY ‘pootlepassword’;FLUSH PRIVILEGES;

Edit the Pootle configuration file to reflect our database backend:

(env)root$ nano ~/.pootle/pootle.conf

Change the DATABASES section to the following:

# Database backend settingsDATABASES = { 'default': { # Replace 'sqlite3' with 'postgresql_psycopg2', 'mysql' or 'oracle'. 'ENGINE': 'django.db.backends.mysql', # Database name or path to database file if using sqlite3. 'NAME': 'pootle', # Not used with sqlite3. 'USER': 'pootle', # Not used with sqlite3. 'PASSWORD': 'pootlepassword', # Set to empty string for localhost. Not used with sqlite3. 'HOST': '', # Set to empty string for default. Not used with sqlite3. 'PORT': '', }}

WSGIRestrictEmbedded On
WSGIPythonOptimize 1
<VirtualHost *:80>
# Domain for the Pootle server. Use 'localhost' for local deployments.
#
# If you want to deploy on example.com/your-pootle/ rather than in
# my-pootle.example.com/ you will have to do the following changes to
# this sample Apache configuration:
#
# - Change the ServerName directive to:
# ServerName example.com
# - Change the WSGIScriptAlias directive to (note that /your-pootle must
# not end with a slash):
# WSGIScriptAlias /your-pootle /var/www/pootle/wsgi.py
# - Change the Alias and Location directives for 'export', and the Alias
# directive for 'assets' to include the '/your-pootle'.
# - Include the following setting in your custom Pootle settings:
# STATIC_URL = '/your-pootle/assets/'
ServerName my-pootle.example.com
# Set the 'POOTLE_SETTINGS' environment variable pointing at your custom
# Pootle settings file.
#
# If you don't know which settings to include in this file you can use
# the file '90-local.conf.sample' as a starting point. This file can be
# found at '/var/www/pootle/env/lib/python2.7/site-packages/pootle/settings/'.
#
# Another way to specify your custom settings is to comment this
# directive and add a new '90-local.conf' file (by copying the file
# '90-local.conf.sample' and changing the desired settings) in
# '/var/www/pootle/env/lib/python2.7/site-packages/pootle/settings/'
# (default location for a pip-installed Pootle, having Python 2.7).
#
# This might require enabling the 'env' module.
SetEnv POOTLE_SETTINGS /var/www/pootle/your_custom_settings.conf
# The following two optional lines enable the "daemon mode" which
# limits the number of processes and therefore also keeps memory use
# more predictable.
WSGIDaemonProcess pootle processes=2 threads=3 stack-size=1048576 maximum-requests=500 inactivity-timeout=300 display-name=%{GROUP} python-path=/var/www/pootle/env/lib/python2.7/site-packages
WSGIProcessGroup pootle
# Point to the WSGI loader script.
WSGIScriptAlias / /var/www/pootle/wsgi.py
# Turn off directory listing by default.
Options -Indexes
# Set expiration for some types of files.
# This might require enabling the 'expires' module.
ExpiresActive On
ExpiresByType image/jpg "access plus 2 hours"
ExpiresByType image/png "access plus 2 hours"
ExpiresByType text/css "access plus 10 years"
ExpiresByType application/x-javascript "access plus 10 years"
# Optimal caching by proxies.
# This might require enabling the 'headers' module.
Header set Cache-Control "public"
# Directly serve static files like css and images, no need to go
# through mod_wsgi and Django. For high performance consider having a
# separate server.
Alias /assets /var/www/pootle/env/lib/python2.7/site-packages/pootle/assets
<Directory /var/www/pootle/env/lib/python2.7/site-packages/pootle/assets>
Order deny,allow
Allow from all
</Directory>
# Allow downloading translation files directly.
# This location must be the same in the Pootle 'PODIRECTORY' setting.
Alias /export /var/www/pootle/env/lib/python2.7/site-packages/pootle/po
<Directory /var/www/pootle/env/lib/python2.7/site-packages/pootle/po>
Order deny,allow
Allow from all
</Directory>
<Location /export>
# Compress before being sent to the client over the network.
# This might require enabling the 'deflate' module.
SetOutputFilter DEFLATE
# Enable directory listing.
Options Indexes
</Location>
</VirtualHost>

In order for this to work we need to enable a couple of Apache2 modules:

(env)root$ a2enmod expires(env)root$ a2enmod headers

Now we need to create the wsgi runner to launch the Pootle application when we access the site:

(env)root$ nano /var/www/pootle/wsgi.py

Type the following into the editor:

#!/usr/bin/env python
# -*- coding: utf-8 -*-
import os
import site
import sys
# You probably will need to change these paths to match your deployment,
# most likely because of the Python version you are using.
ALLDIRS = [
'/var/www/pootle/env/lib/python2.7/site-packages',
'/var/www/pootle/env/lib/python2.7/site-packages/pootle/apps',
]
# Remember original sys.path.
prev_sys_path = list(sys.path)
# Add each new site-packages directory.
for directory in ALLDIRS:
site.addsitedir(directory)
# Reorder sys.path so new directories at the front.
new_sys_path = []
for item in list(sys.path):
if item not in prev_sys_path:
new_sys_path.append(item)
sys.path.remove(item)
sys.path[:0] = new_sys_path
# Set the Pootle settings module as DJANGO_SETTINGS_MODULE.
os.environ['DJANGO_SETTINGS_MODULE'] = 'pootle.settings'
# Set the WSGI application.
def application(environ, start_response):
"""Wrapper for Django's WSGIHandler().
This allows to get values specified by SetEnv in the Apache
configuration or interpose other changes to that environment, like
installing middleware.
"""
try:
os.environ['POOTLE_SETTINGS'] = environ['POOTLE_SETTINGS']
except KeyError:
pass
from django.core.wsgi import get_wsgi_application
_wsgi_application = get_wsgi_application()
return _wsgi_application(environ, start_response)

The new Redmine 2.0.0 release now supports Rails 3.2.3 and that, along with a few other changes, makes the installation route slightly different.

As stated before, I AM NOT a Linux/Ubuntu guru, so any mistakes are of my own making and I’d appreciate any feedback to make the installation better/clearer.

So, with all that said, here goes:

I know that Redmine can be installed as a package in Ubuntu, but it doesn’t appear to be the latest version (1.4.2 at the time of writing). So I’m taking the longer route to get it working, as I couldn’t get it to configure the way I want. It does have the advantage that I’m using the very latest version straight from RubyForge.

For this install, I’m using a fresh install of Ubuntu 12.04 LTS, configured as a LAMP server, so Apache, MySQL & PHP are already installed.
Get into the folder where we’re going to install & configure Redmine from:

cd /usr/share

Now we’re going to download the latest version of Redmine from RubyForge:

The following instructions have been cobbled together from various sources (plus my own random thoughts) and has FINALLY got me a working Redmine installation under Ubuntu 10.10.

I’m far from a Linux/Ubuntu guru so I’d welcome any input/suggestions/corrections to make it better and to correct any mistakes.

Here goes:

I know that Redmine can be installed as a package in Ubuntu, but it doesn’t appear to be the latest version (1.1.0 at the time of writing). So I’m taking the longer route to get it working, as I couldn’t get it to configure the way I want. It does have the advantage that I’m using the very latest version straight from RubyForge.