Pootle on Fedora ================ Welcome to Pootle running on Fedora. This README offers some Fedora specific information on Pootle. 0. Installation setup - Database You can use MySQL (recommended) or Sqlite. Sqlite requires no setup. If you want to use MySQL then see section 3. below. - Email You need email for user registration confirmations, edit EMAIL_* and DEFAULT_FROM_EMAIL in /etc/pootle/localsettings.py 1. Running Pootle Regardless of how you choose to run Pootle (see below) the first run will be slow. This is because the Django database is initialised and the statistics are generated for all files. This is a once off event with subsequent operations being much faster. To run Pootle you can use Apache or run Pootle standalone: - Apache (recommended) Before running ensure that apache and memcached are running $ services httpd start $ services memcached start Now point your web browser to http://localhost/pootle and Pootle will run. - Standalone (not recommended) Before running ensure that memcached is running $ services memcached start Run PootleServer and Pootle will be available on http://localhost:8080 While you can run either of these ways it is recommended that you don't mix and match as you can get problems with file permission. Rather stick to one approach. 2. Post installation 2.1 Default administrative password Your administrative user is username: admin, password: admin. Make sure that you change that before going live. 2.2 SELinux 2.2.1 Accessing memcached Pootle is configured on Fedora to use memcached, but Apache will not be able to access memcached by default if you are using SELinux. To allow Pootle to access memcached you will need to run the following command: $ setsebool -P httpd_can_network_memcache 1 or, if that fails try: $ setsebool -P httpd_can_network_relay 1 Alternatively youu can run memcached using Unix sockets: http://translate.sourceforge.net/wiki/pootle/cache#memcached 2.2.2 Writing translation files in /var/lib/pootle/po This shouldn't be needed by default but if Pootle has trouble accessing files in /var/lib/pootle/po then run: $ chcon -R -t httpd_sys_content_rw_t /var/lib/pootle/po 3. Optimising Pootle To make Pootle go faster, especially on larger installations you will want to do the following: - Review optimisation hints Pootle provides admins with various tips for optimisation, check that your setup is running optimally by visiting: http://localhost/pootle/admin/ - MySQL database Pootle will by default use a sqlite database. If you move to MySQL (or another RDBMS) you should see improved performance. Follow the setup instructions at http://translate.sourceforge.net/wiki/pootle/using_mysql 4. Further information 4.1 Command line power for Pootle A number of commands are available to help you batch process actions on Pootle as well as when building your own scripts. http://translate.sourceforge.net/wiki/pootle/commands 4.2 Pootle and Version Control The wiki has a lot of information on setting up the version control system http://translate.sourceforge.net/wiki/pootle/version_control 4.3 Pootle and Translation Memory (TM) The updatetm tool is what you want to use to supply translation memory suggestions to translators: http://translate.sourceforge.net/wiki/pootle/updatetm 4.4 Terminology You can setup a terminology project or terminology file to supply terminology suggestions to translators: http://translate.sourceforge.net/wiki/pootle/adding_a_terminology_project 4.5 Changes to Pootle on Fedora The following changes have been made to a default Pootle setup Optimisations: - memcached - this is used by default for better performance - apache - while Pootle can run standalone Apache provides better performance so we have made that standard. - Xapian - for indexing searches otherwise they're quite slow - Session stores - we store them in memcached for speed Important files: /etc/pootle/localsettings.py - Pootle configuration file /var/lib/pootle/dbs/pootle.db - your Pootle database: config, users, translations, etc Projects: /var/lib/pootle/po/$project - your translation project files -- Enjoy, Pootle developers