[Python-apps-commits] r3812 - in packages/trac/trunk/debian (README.Debian)

[techtonik-guest at users.alioth.debian.org]

    Date: Tuesday, September 22, 2009 @ 20:57:43
  Author: techtonik-guest
Revision: 3812

* update Trac Debian info

Modified:
  packages/trac/trunk/debian/README.Debian

Modified: packages/trac/trunk/debian/README.Debian
===================================================================
--- packages/trac/trunk/debian/README.Debian	2009-09-22 20:57:39 UTC (rev 3811)
+++ packages/trac/trunk/debian/README.Debian	2009-09-22 20:57:43 UTC (rev 3812)
@@ -1,4 +1,3 @@
-
 Configuring Trac on Debian
 ==========================
   Trac is a web-based project management tool. It can be run as a
@@ -15,19 +14,21 @@
 
 Creating a Project Environment
 ------------------------------
-  Trac Environment is the backend storage format where Trac stores 
-information like wiki pages, tickets, reports, settings, etc. 
-  A Trac environment consists of a directory containing a SQLite 
-database, human-readable configuration file, log-files and 
-attachments.
+  Trac Environment is the backend storage that contains information
+related to specific project like settings, wiki pages, tickets,
+templates, etc. 
+  A Trac environment consists of a directory with human-readable
+configuration file, default SQLite database, log files, attachments,
+plugins (if any) and custom templates.
 
-  Trac allows the use of many backend Version Control Systems (vcs).
-By default only Subversion is supported. Others like git 
-(trac-git), bzr (trac-bzr) and Mercurial (trac-mercurial) can be 
-added as plugin.
+  Trac can visualize contents of many Version Control Systems (vcs)
+repositories. By default it supports only Subversion. Plugins can be
+added to support git (trac-git), bzr (trac-bzr) or Mercurial
+(trac-mercurial).
 
-  Before creating a Trac environment, you need to have a vcs
-repository. With Subversion this can be made with:
+  Trac can work without vcs repository, but you may want to create
+one for you project before creating a Trac environment. With
+Subversion this can be made with:
 
     $ mkdir /path/to/repos
     $ svnadmin create /path/to/repos
@@ -36,19 +37,21 @@
 
     $ trac-admin /path/to/projectenv initenv
 
-NOTE: The web server user needs write permission to the environment directory
-and all the files inside. After creating the environment you would need to 
-execute "chown -R www-data /path/to/projectenv" if trac-admin was executed as
-another user.
+NOTE: The web server user (usually "www-data" for Apache) needs write
+permission to the environment directory and all the files inside.
+After creating the environment you would need to execute
+"chown -R www-data /path/to/projectenv" if trac-admin was executed as
+a different user than "www-data".
 
-trac-admin will ask you where your subversion repository is located and where
-it can find the trac templates directory (the default value should be fine).
+trac-admin will ask you some questions to setup the environment
+(defaults should be ok).
 
 Configuring Apache Web Server
 =============================
 
-Apache is the preferred trac's webserver and most used too.
-It can be configured in 2 groups: as CGI (CGI, WSGI, FCGI) and with mod-python.
+Apache is the most used webserver, so it's preferred for Trac.
+It can be configured to be run as CGI application (CGI, WSGI, FCGI)
+or with mod-python.
 
 Configuring as CGI, WSGI, FCGI
 --------------------------------