[pootle] Updated README.fedora with more SELinux information

[dwayne]

commit 946a1d26bd0459b486ed246c1f9861fba8a85d0f
Author: Dwayne Bailey <dwayne at translate.org.za>
Date:   Sat Sep 4 12:24:58 2010 +0200

    Updated README.fedora with more SELinux information

 README.fedora |   33 +++++++++++++++++++++++++--------
 pootle.spec   |    5 ++++-
 2 files changed, 29 insertions(+), 9 deletions(-)
---
diff --git a/README.fedora b/README.fedora
index 7f4fb71..5cb37f7 100644
--- a/README.fedora
+++ b/README.fedora
@@ -19,7 +19,7 @@ and DEFAULT_FROM_EMAIL in /etc/pootle/localsettings.py
 
 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 
+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:
@@ -36,7 +36,7 @@ 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 
+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.
 
@@ -50,12 +50,29 @@ 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 memceched by default if you are using SELinux.  To
+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_connect 1
+$ 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
@@ -90,7 +107,7 @@ 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 
+The updatetm tool is what you want to use to supply translation memory
 suggestions to translators:
 http://translate.sourceforge.net/wiki/pootle/updatetm
 
@@ -114,9 +131,9 @@ Optimisations:
 - 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
+/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
diff --git a/pootle.spec b/pootle.spec
index 4587fb6..4d5b4ff 100644
--- a/pootle.spec
+++ b/pootle.spec
@@ -4,7 +4,7 @@
 
 Name:           pootle
 Version:        2.1.1
-Release:        1%{?dist}
+Release:        2%{?dist}
 Summary:        Localization and translation management web application
 
 Group:          Development/Tools
@@ -128,6 +128,9 @@ fi
 
 
 %changelog
+* Sat Sep 4 2010 Dwayne Bailey <dwayne at translate.org.za> - 2.1.1-2
+- Updated README.fedora with more SELinux information
+
 * Sat Sep 4 2010 Dwayne Bailey <dwayne at translate.org.za> - 2.1.1-1
 - Update to 2.1.1
    - Ability to migrate data between different database engines