tag 629914 + patch thanks I checkout out the packaging for 2.1.6 and installed it. Here is my rewrite of README.Debian given my experiences.
I suggest removing the pootle.prefs and users.prefs files entirely, as they are obsolete--Pootle hasn't actually referred to them since it was ported to Django. I also dropped the paragraph about the HTTP server because it didn't really seem that useful... putting web services behind HTTPS is just common sense and advice about doing so doesn't have to go in every single web application package. But I don't really care strongly about this one way or the other. :) Pootle server configuration =========================== Pootle's configuration file can be found at '/etc/pootle/localsettings.py'. Be sure to configure DEFAULT_FROM_EMAIL so that users will be able to register on the server. You should also configure CACHE_BACKEND based on your choice of database and the size of your installation. Small installations can leave CACHE_BACKEND unset to use the local memory backend, but but if you have many projects/users/translations then you should use the database cache backend (not with PostgreSQL, see <https://code.djangoproject.com/ticket/11569>) or memcached. The server will initially have a single user, 'admin'. This user's password may be set by using the 'changepassword' action for the django-admin command: django-admin changepassword admin --settings=pootle.settings This should be run as the 'pootle' user, for example with su(1) or sudo(1). The server will not run automatically unless you set POOTLE_ENABLE in '/etc/default/pootle' to 'Yes'. -- Sam Morris <[email protected]> -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
