Installation instructions


Install all required components (see above) and adjust You will probably want to adjust following options:


List of site administrators to receive notifications when something goes wrong, for example notifications on failed merge or Django errors.


Connectivity to database server, please check Django’s documentation for more details.


When using MySQL, don’t forget to create database with UTF-8 encoding:



Disable this for production server.


Email sender address for outgoing email, for example registration emails.


Email used as sender address for sending emails to administrator, for example notifications on failed merge.

After your configuration is ready, you can run ./ syncdb to create database structure. Now you should be able to create translation projects using admin interface.

You should also login to admin interface (on /admin/ URL) and adjust default site name to match your domain.

See also

Access control

Running server

Running Weblate is not different from running any other Django based application.

It is recommended to serve static files directly by your webserver, you should use that for following paths:

Serves media directory from Weblate.
Serves media files for Django admin interface (eg. /usr/share/pyshared/django/contrib/admin/media/).

Additionally you should setup rewrite rule to serve media/favicon.ico as favicon.ico.

Sample configuration for Lighttpd

The configuration for Lighttpd web server might look like following (available as examples/lighttpd.conf):

fastcgi.server = (
    "/weblate.fcgi" => (
        "main" => (
            "socket" => "/var/run/django/weblate.socket",
            "check-local" => "disable",
alias.url = (
    "/media" => "/var/lib/django/weblate/weblate/media/",
    "/static/admin" => "/usr/share/pyshared/django/contrib/admin/static/admin/",

url.rewrite-once = (
    "^(/*media.*)$" => "$1",
    "^(/*static.*)$" => "$1",
    "^/*favicon\.ico$" => "/media/favicon.ico",
    "^/*robots\.txt$" => "/media/robots.txt",
    "^(/.*)$" => "/weblate.fcgi$1",

expire.url                  = (
    "/media/" => "access 1 months",
    "/static/" => "access 1 months",
    "/favicon.ico" => "access 1 months",

Sample configuration for Apache

Following configuration runs Weblate as WSGI, you need to have enabled mod_wsgi (available as examples/apache.conf):

# VirtualHost for weblate
WSGIPythonPath /usr/share/weblate
<VirtualHost *:80>

    DocumentRoot /usr/share/weblate/weblate/media/

    Alias /robots.txt /usr/share/weblate/weblate/media/robots.txt
    Alias /favicon.ico /usr/share/weblate/weblate/media/favicon.ico

    Alias /media/ /usr/share/weblate/weblate/media/
    Alias /doc/ /usr/share/doc/packages/weblate/html/
    Alias /static/admin /usr/lib/python2.7/site-packages/django/contrib/admin/static/admin/

    <Directory /usr/lib/python2.7/site-packages/django/contrib/admin/static/admin/>
        Order deny,allow
        Allow from all

    <Directory /usr/share/weblate/weblate/media/>
        Order deny,allow
        Allow from all

    <Directory /usr/share/doc/packages/weblate/html/>
        Order deny,allow
        Allow from all

    <Directory /usr/share/weblate/weblate/examples/>
        Order deny,allow
        Allow from all

    WSGIScriptAlias / /usr/share/weblate/weblate/
    WSGIPassAuthorization On

    <Directory /usr/share/weblate/weblate>
        Order deny,allow
        Allow from all


Prebuilt appliance

Prebuilt appliance provides preconfigured Weblate running with MySQL database as backend and Apache as webserver. However it comes with standard set of passwords you will want to change:

Username Password Scope Description
root linux System Administrator account, use for local or SSH login
root   MySQL MySQL administrator
weblate weblate MySQL Account in MySQL database for storing Weblate data
admin admin Weblate Weblate/Django admin user

The appliance is built using SUSE Studio and is based on openSUSE 12.1.


On upgrade to version 0.6 you should run ./ syncdb and ./ setupgroups –move to setup access control as described in installation section.

On upgrade to version 0.7 you should run ./ syncdb to setup new tables and ./ rebuild_index to build index for fulltext search.

On upgrade to version 0.8 you should run ./ syncdb to setup new tables, ./ setupgroups to update privileges setup and ./ rebuild_index to rebuild index for fulltext search.

On upgrade to version 0.9 file structure has changed. You need to move repos and whoosh-index to weblate folder. Also running ./ syncdb, ./ setupgroups and ./ setuplang is recommended to get latest updates of privileges and language definitions.

On upgrade to version 1.0 one field has been added to database, you need to invoke following SQL command to adjust it:

ALTER TABLE `trans_subproject` ADD `template` VARCHAR(200);

Migrating from Pootle

As Weblate was originally written as replacement from Pootle, it is supported to migrate user accounts from Pootle. All you need to do is to copy auth_user table from Pootle, user profiles will be automatically created for users as they log in and they will be asked to update their settings.

Project Versions

Table Of Contents

Previous topic

Quick starting guide

Next topic


This Page