rpms/pootle/devel README.fedora, NONE, 1.1 import.log, NONE, 1.1 pootle-2.0.0-rc2-fedora-settings.patch, NONE, 1.1 pootle.conf, NONE, 1.1 pootle.spec, NONE, 1.1 .cvsignore, 1.1, 1.2 sources, 1.1, 1.2
dwayne
dwayne at fedoraproject.org
Sun Jan 17 19:16:09 UTC 2010
Author: dwayne
Update of /cvs/pkgs/rpms/pootle/devel
In directory cvs1.fedora.phx.redhat.com:/tmp/cvs-serv29733/devel
Modified Files:
.cvsignore sources
Added Files:
README.fedora import.log
pootle-2.0.0-rc2-fedora-settings.patch pootle.conf pootle.spec
Log Message:
Initial import (#533594).
--- NEW FILE README.fedora ---
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 sqlite (default) or MySQL. 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 files statistics are generated. 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
Your administrative user is username: admin, password: admin. Make sure
that you change that before going live.
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 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.2 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.3 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.4 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/stats.db - your statistics cache
/var/lib/pootle/dbs/pootle.db - your Django config, users, etc
Projects:
/var/lib/pootle/po/$project - your translation project files
--
Enjoy,
Pootle developers
--- NEW FILE import.log ---
pootle-2_0_1-2_fc12:HEAD:pootle-2.0.1-2.fc12.src.rpm:1263755565
pootle-2.0.0-rc2-fedora-settings.patch:
localsettings.py | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
--- NEW FILE pootle-2.0.0-rc2-fedora-settings.patch ---
diff -up Pootle-2.0.0-rc2/localsettings.py.fedora-settings Pootle-2.0.0-rc2/localsettings.py
--- Pootle-2.0.0-rc2/localsettings.py.fedora-settings 2009-11-25 13:27:26.000000000 +0200
+++ Pootle-2.0.0-rc2/localsettings.py 2009-11-27 16:02:58.000000000 +0200
@@ -56,10 +56,10 @@ PARSE_POOL_CULL_FREQUENCY = 4
# By default we use Django's in memory cache which is only suitable
# for small deployments. memcached is prefered. For more info, check
# http://docs.djangoproject.com/en/dev/topics/cache/#setting-up-the-cache
-CACHE_BACKEND = 'locmem:///?max_entries=4096&cull_frequency=5'
+#CACHE_BACKEND = 'locmem:///?max_entries=4096&cull_frequency=5'
# Uncomment to use memcached for caching
-#CACHE_BACKEND = 'memcached://127.0.0.1:11211/'
+CACHE_BACKEND = 'memcached://127.0.0.1:11211/'
# Using memcached to store sessions improves performance for anonymous
# users. For more info, check
@@ -69,7 +69,7 @@ CACHE_BACKEND = 'locmem:///?max_entries=
#SESSION_ENGINE = 'django.contrib.sessions.backends.cache'
# Uncomment this if you're using memcached as CACHE_BACKEND and running under Django 1.1
-#SESSION_ENGINE = 'django.contrib.sessions.backends.cached_db'
+SESSION_ENGINE = 'django.contrib.sessions.backends.cached_db'
# To improve performance, non-logged users get cached copies of most pages.
# This variable is the number of seconds for which a page will be reused from
--- NEW FILE pootle.conf ---
WSGIScriptAlias /pootle /usr/share/pootle/wsgi.py
<Directory /usr/share/pootle>
Order deny,allow
Allow from all
</Directory>
Alias /pootle/html /usr/share/pootle/html
<Directory /usr/share/pootle/html>
Order deny,allow
Allow from all
</Directory>
Alias /pootle/export /var/lib/pootle/po
<Directory "/var/lib/pootle/po">
Order deny,allow
Allow from all
</Directory>
<IfModule mod_deflate.c>
<location /pootle/html>
SetOutputFilter DEFLATE
</location>
<location /pootle/export>
SetOutputFilter DEFLATE
</location>
</IfModule>
--- NEW FILE pootle.spec ---
%{!?python_sitelib: %define python_sitelib %(%{__python} -c "from distutils.sysconfig import get_python_lib; print get_python_lib()")}
%global fullname Pootle
Name: pootle
Version: 2.0.1
Release: 2%{?dist}
Summary: Localization and translation management web application
Group: Development/Tools
License: GPLv2+
URL: http://translate.sourceforge.net/wiki/pootle/index
Source: http://downloads.sourceforge.net/project/translate/%{fullname}/%{version}/%{fullname}-%{version}.tar.bz2
Source1: pootle.conf
Source2: README.fedora
BuildRoot: %{_tmppath}/%{name}-%{version}-%{release}-root-%(%{__id_u} -n)
Patch0: pootle-2.0.0-rc2-fedora-settings.patch
BuildArch: noarch
BuildRequires: python-devel
BuildRequires: translate-toolkit >= 1.4.1
Requires: Django >= 1.0
Requires: iso-codes
Requires: memcached
Requires: mod_wsgi
Requires: python-lxml
Requires: python-memcached
Requires: python-Levenshtein
Requires: translate-toolkit >= 1.5.1
Requires: xapian-bindings-python >= 1.0.13
Requires: xapian-core
Requires: zip
# This is for /sbin/service
Requires(post): initscripts
Requires(postun): initscripts
%description
Pootle is web application for managing distributed or crowdsourced
translation.
It's features include::
* Translation of Gettext PO and XLIFF files.
* Submitting to remote version control systems (VCS).
* Managing groups of translators
* Online webbased or offline translation
* Quality checks
%prep
%setup -q -n %{fullname}-%{version}
%patch0 -p1 -b .fedora-settings
%build
%{__python} setup.py build
%install
rm -rf $RPM_BUILD_ROOT
%{__python} setup.py install -O1 --skip-build --root $RPM_BUILD_ROOT
# Create the manpages
mkdir -p $RPM_BUILD_ROOT/%{_mandir}/man1
for program in $RPM_BUILD_ROOT/%{_bindir}/*;
do
case $(basename $program) in
PootleServer|import_pootle_prefs)
;;
*)
LC_ALL=C PYTHONPATH=. $program --manpage \
> $RPM_BUILD_ROOT/%{_mandir}/man1/$(basename $program).1 \
|| rm -f $RPM_BUILD_ROOT/%{_mandir}/man1/$(basename $program).1
;;
esac
done
install -d $RPM_BUILD_ROOT%{_sbindir} $RPM_BUILD_ROOT%{_datadir}/pootle/ $RPM_BUILD_ROOT%{_sharedstatedir}/pootle $RPM_BUILD_ROOT%{_sysconfdir}/pootle
install $RPM_BUILD_ROOT%{_bindir}/PootleServer $RPM_BUILD_ROOT%{_sbindir}
rm $RPM_BUILD_ROOT%{_bindir}/PootleServer
install -p --mode=644 %{SOURCE1} -D $RPM_BUILD_ROOT%{_sysconfdir}/httpd/conf.d/pootle.conf
install wsgi.py $RPM_BUILD_ROOT%{_datadir}/pootle/
cp -p %{SOURCE2} .
%clean
rm -rf $RPM_BUILD_ROOT
%post
/sbin/service httpd restart >/dev/null 2>&1 || :
/sbin/service memcached restart >/dev/null 2>&1 || :
%postun
if [ "$1" -ge "1" ] ; then
/sbin/service httpd condrestart >/dev/null 2>&1 || :
/sbin/service memcached condrestart >/dev/null 2>&1 || :
fi
%files
%defattr(-,root,root,-)
%doc COPYING ChangeLog README README.fedora
%{_bindir}/*
%{_sbindir}/*
%{_mandir}/man1/*
%config(noreplace) %{_sysconfdir}/pootle
%config(noreplace) %{_sysconfdir}/httpd/conf.d/pootle.conf
%{python_sitelib}/*
%{_datadir}/pootle
%attr(-,apache,apache) %{_sharedstatedir}/pootle
# We exclude docs as the Pootle installer doesn't do ${name}-${version} as expected in Fedora
%exclude %{_datadir}/doc/pootle
%changelog
* Thu Jan 14 2010 Dwayne Bailey <dwayne at translate.org.za> - 2.0.1-2
- Fixes from spec review
* Thu Jan 14 2010 Dwayne Bailey <dwayne at translate.org.za> - 2.0.1-1
- Update to 2.0.1
* Mon Dec 7 2009 Dwayne Bailey <dwayne at translate.org.za> - 2.0.0-1
- Update to 2.0.0 final
- Prefer running under Apache and drop standalone supporting infrastructure
* Fri Nov 27 2009 Dwayne Bailey <dwayne at translate.org.za> - 2.0.0-0.1.rc2
- Update to 2.0.0 rc2
* Thu Nov 5 2009 Dwayne Bailey <dwayne at translate.org.za> - 1.3.0-0.3
- Depend on mod_wsgi
* Mon Nov 2 2009 Dwayne Bailey <dwayne at translate.org.za> - 1.3.0-0.2
- Update to 1.3.0 beta4
- Enable mod_wsgi operation: require httpd, default pootle.conf
- Backport DB initialisation
- Add dependencies for performance: memcached, Levenshtein, xapian
- Fedora README
* Thu Jan 8 2009 Dwayne Bailey <dwayne at translate.org.za> - 1.3.0-0.1
- Django based Pootle
* Mon Oct 6 2008 Dwayne Bailey <dwayne at translate.org.za> - 1.2.0-1
- Update to final 1.2.0 release
* Tue Sep 30 2008 Dwayne Bailey <dwayne at translate.org.za> - 1.2.0-0.5.rc1
- Update to RC1
* Tue Sep 2 2008 Dwayne Bailey <dwayne at translate.org.za> - 1.2.0-0.4.beta2
- Create run_pootle.sh wrapper for server
* Wed Aug 27 2008 Dwayne Bailey <dwayne at translate.org.za> - 1.2.0-0.3.beta2
- Create man pages
- Rebuild with a refreshed tarball that contains jquery
* Wed Aug 27 2008 Dwayne Bailey <dwayne at translate.org.za> - 1.2.0-0.2.beta2
- Update to 1.2.0-beta2
- Fix initscript installation location
* Sun Aug 24 2008 Dwayne Bailey <dwayne at translate.org.za> - 1.2.0-0.1.beta1
- Build for 1.2.0-beta1 release
- Create initscripts, sysconfig; create proper logging; configure stats database
* Thu Feb 14 2008 Dwayne Bailey <dwayne at translate.org.za> - 1.0.2-1
- Rebuild for fc9
* Thu Feb 14 2008 Dwayne Bailey <dwayne at translate.org.za> - 1.0.2-1
- Initial packaging
Index: .cvsignore
===================================================================
RCS file: /cvs/pkgs/rpms/pootle/devel/.cvsignore,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -p -r1.1 -r1.2
--- .cvsignore 16 Jan 2010 00:56:03 -0000 1.1
+++ .cvsignore 17 Jan 2010 19:16:08 -0000 1.2
@@ -0,0 +1 @@
+Pootle-2.0.1.tar.bz2
Index: sources
===================================================================
RCS file: /cvs/pkgs/rpms/pootle/devel/sources,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -p -r1.1 -r1.2
--- sources 16 Jan 2010 00:56:03 -0000 1.1
+++ sources 17 Jan 2010 19:16:09 -0000 1.2
@@ -0,0 +1 @@
+756c1646fec06750eac7b6c0846c2b50 Pootle-2.0.1.tar.bz2
More information about the scm-commits
mailing list