Translate Toolkit & Pootle

Tools to help you make your software local

User Tools

Mozoolte Django migration

The information on this page is kept for historical interest. Pootle is in the process of being ported to Django. See The Great Pootle Migration.

This page documents steps we can take in the initial migration of Mozootle to Django. The motivation is a reduction in pain.

For information gathered earlier about Django migration, see Django migration.

  1. Only use Django's URL dispatch mechanism to route all calls to the getpage function in This implies a single file with two entries - the url for the admin interface and a wildcard directing everything else to getpage.
  2. In order to make the above work, authentication & sessions are needed. Use Django's modules. Django's authentication module is relatively flexible and allows the user to specify authentication functions (which means that we can deal with LDAP).

Q&A from IRC

(10:42:10) friedel1: Winterstream1: So we can continue with sqlalchemy and already have something useful before we switch ORM?

Yes, but we won't get the benefits of Django's admin interface for our software models based on SQLAlchemy.

(10:42:10) clouserw: step #1 won't interfere with django's admin interface, right?

This refers to step 1 above. The description as been fixed to point out that we still need to point to the admin page. It shouldn't impact negatively on the admin interface otherwise.