Changes between Version 6 and Version 7 of TracInstall


Ignore:
Timestamp:
Jan 12, 2016, 11:21:52 PM (4 years ago)
Author:
trac
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • TracInstall

    v6 v7  
    1 = Trac Installation Guide for 1.0
    2 
     1= Trac Installation Guide for 1.0 =
    32[[TracGuideToc]]
    43
    54Trac is written in the Python programming language and needs a database, [http://sqlite.org/ SQLite], [http://www.postgresql.org/ PostgreSQL], or [http://mysql.com/ MySQL]. For HTML rendering, Trac uses the [http://genshi.edgewall.org Genshi] templating system.
    65
    7 Since version 0.12, Trac can also be localized, and there is probably a translation available in your language. If you want to use the Trac interface in other languages, then make sure you have installed the optional package [#OtherPythonPackages Babel]. Pay attention to the extra steps for localization support in the [#InstallingTrac Installing Trac] section below. Lacking Babel, you will only get the default English version.
    8 
    9 If you're interested in contributing new translations for other languages or enhancing the existing translations, then please have a look at [trac:wiki:TracL10N TracL10N].
    10 
    11 What follows are generic instructions for installing and setting up Trac. While you may find instructions for installing Trac on specific systems at [trac:TracInstallPlatforms TracInstallPlatforms] on the main Trac site, please '''first read through these general instructions''' to get a good understanding of the tasks involved.
     6Since version 0.12, Trac can also be localized, and there's probably a translation available for your language. If you want to be able to use the Trac interface in other languages, then make sure you have installed the optional package [#OtherPythonPackages Babel]. Pay attention to the extra steps for localization support in the [#InstallingTrac Installing Trac] section below. Lacking Babel, you will only get the default english version, as usual.
     7
     8If you're interested in contributing new translations for other languages or enhance the existing translations, then please have a look at [[trac:TracL10N]].
     9
     10What follows are generic instructions for installing and setting up Trac and its requirements. While you may find instructions for installing Trac on specific systems at [trac:TracInstallPlatforms TracInstallPlatforms] on the main Trac site, please be sure to '''first read through these general instructions''' to get a good understanding of the tasks involved.
    1211
    1312[[PageOutline(2-3,Installation Steps,inline)]]
    1413
    15 == Dependencies
    16 
     14== Dependencies ==
    1715=== Mandatory Dependencies
    18 
    1916To install Trac, the following software packages must be installed:
    2017
    2118 * [http://www.python.org/ Python], version >= 2.5 and < 3.0
    2219   (note that we dropped the support for Python 2.4 in this release)
    23  * [http://pypi.python.org/pypi/setuptools setuptools], version >= 0.6
    24  * [http://genshi.edgewall.org/wiki/Download Genshi], version >= 0.6
    25 
    26 You also need a database system and the corresponding python bindings. The database can be either SQLite, PostgreSQL or MySQL.
     20 * [http://peak.telecommunity.com/DevCenter/setuptools setuptools], version >= 0.6, or better yet, [http://pypi.python.org/pypi/distribute distribute]
     21 * [http://genshi.edgewall.org/wiki/Download Genshi], version >= 0.6 (unreleased version 0.7dev should work as well)
     22
     23You also need a database system and the corresponding python bindings.
     24The database can be either SQLite, PostgreSQL or MySQL.
    2725
    2826==== For the SQLite database #ForSQLite
    2927
    30 As you must be using Python 2.5, 2.6 or 2.7, you already have the SQLite database bindings bundled with the standard distribution of Python: the `sqlite3` module.
    31 
    32 Optionally, you may install a newer version of [http://pypi.python.org/pypi/pysqlite pysqlite] than the one provided by the Python distribution. See [trac:PySqlite#ThePysqlite2bindings PySqlite] for details.
     28As you must be using Python 2.5, 2.6 or 2.7, you already have the SQLite database bindings bundled with the standard distribution of Python (the `sqlite3` module).
     29
     30However, if you'd like, you can download the latest and greatest version of [[trac:Pysqlite]] from
     31[http://code.google.com/p/pysqlite/downloads/list google code], where you'll find the Windows
     32installers or the `tar.gz` archive for building from source:
     33{{{
     34$ tar xvfz <version>.tar.gz
     35$ cd <version>
     36$ python setup.py build_static install
     37}}}
     38 
     39This will download the latest SQLite code and build the bindings.
     40
     41SQLite 2.x is no longer supported.
     42
     43A known bug PySqlite versions 2.5.2-4 prohibits upgrade of trac databases
     44from 0.11.x to 0.12. Please use versions 2.5.5 and newer or 2.5.1 and
     45older. See #9434 for more detail.
     46
     47See additional information in [trac:PySqlite PySqlite].
    3348
    3449==== For the PostgreSQL database #ForPostgreSQL
     
    3651You need to install the database and its Python bindings:
    3752 * [http://www.postgresql.org/ PostgreSQL], version 8.0 or later
    38  * [http://pypi.python.org/pypi/psycopg2 psycopg2], version 2.0 or later
     53 * [http://pypi.python.org/pypi/psycopg2 psycopg2]
    3954
    4055See [trac:DatabaseBackend#Postgresql DatabaseBackend] for details.
    4156
     57
    4258==== For the MySQL database #ForMySQL
    4359
    44 Trac works well with MySQL, provided you follow the guidelines:
    45 
    46  * [http://mysql.com/ MySQL] or [http://mariadb.org/ MariaDB], version 5.0 or later
     60Trac can now work quite well with MySQL, provided you follow the guidelines.
     61
     62 * [http://mysql.com/ MySQL], version 5.0 or later
    4763 * [http://sf.net/projects/mysql-python MySQLdb], version 1.2.2 or later
    4864
    49 Given the caveats and known issues surrounding MySQL, read the [trac:MySqlDb] page before creating the database.
     65It is '''very''' important to read carefully the [trac:MySqlDb] page before creating the database.
    5066
    5167=== Optional Dependencies
    5268
    53 ==== Version Control System
    54 
    55 ===== Subversion
    56  * [http://subversion.apache.org/ Subversion], 1.5.x or later and the '''corresponding''' Python bindings. Older versions starting from 1.0, like 1.2.4, 1.3.2 or 1.4.2, etc. may still work. For troubleshooting information, check the [trac:TracSubversion#Troubleshooting TracSubversion] page.
    57 
    58 There are [http://subversion.apache.org/packages.html pre-compiled SWIG bindings] available for various platforms. (Good luck finding precompiled SWIG bindings for any Windows package at that listing. [trac:TracSubversion] points you to [http://alagazam.net Alagazam], which works for me under Python 2.6.)
     69==== Version Control System ====
     70
     71===== Subversion =====
     72 * [http://subversion.apache.org/ Subversion], 1.5.x or 1.6.x and the '''''corresponding''''' Python bindings. Older versions starting from 1.0, like 1.2.4, 1.3.2 or 1.4.2, etc. should still work. For troubleshooting information, check the [trac:TracSubversion#Troubleshooting TracSubversion] page.
     73
     74There are [http://subversion.apache.org/packages.html pre-compiled SWIG bindings] available for various platforms. (Good luck finding precompiled SWIG bindings for any Windows package at that listing. TracSubversion points you to [http://alagazam.net Algazam], which works for me under Python 2.6.)
    5975
    6076Note that Trac '''doesn't''' use [http://pysvn.tigris.org/ PySVN], neither does it work yet with the newer `ctype`-style bindings.
    6177
    62 '''Note:''' if using Subversion, Trac must be installed on the '''same machine'''. Remote repositories are currently [trac:ticket:493 not supported].
    63 
    64 ===== Git
    65  * [http://git-scm.com/ Git] 1.5.6 or later.
    66 
    67 More information is available on the [trac:TracGit] page.
    68 
    69 ===== Others
    70 
    71 Support for other version control systems is provided via third-parties. See [trac:PluginList#VersionControlSystems] and [trac:VersionControlSystem].
    72 
    73 ==== Web Server
    74 
    75 A web server is optional because Trac has a server included, see the [#RunningtheStandaloneServer Running the Standalone Server] section below.
    76 
    77 Alternatively you can configure Trac to run in any of the following environments:
     78
     79'''Please note:''' if using Subversion, Trac must be installed on the '''same machine'''. Remote repositories are currently [trac:ticket:493 not supported].
     80
     81
     82===== Others =====
     83
     84Support for other version control systems is provided via third-parties. See [trac:PluginList] and [trac:VersionControlSystem].
     85
     86==== Web Server ====
     87A web server is optional because Trac is shipped with a server included, see the [#RunningtheStandaloneServer Running the Standalone Server ] section below.
     88
     89Alternatively you configure Trac to run in any of the following environments.
    7890 * [http://httpd.apache.org/ Apache] with
    7991   - [http://code.google.com/p/modwsgi/ mod_wsgi], see [wiki:TracModWSGI] and
    8092     http://code.google.com/p/modwsgi/wiki/IntegrationWithTrac
    81    - [http://modpython.org/ mod_python 3.5.0], see TracModPython
     93   - [http://modpython.org/ mod_python 3.3.1], deprecated: see TracModPython)
    8294 * a [http://www.fastcgi.com/ FastCGI]-capable web server (see TracFastCgi)
    8395 * an [http://tomcat.apache.org/connectors-doc/ajp/ajpv13a.html AJP]-capable web
    8496   server (see [trac:TracOnWindowsIisAjp TracOnWindowsIisAjp])
    85  * a FastCGI and FastCGI-to-WSGI gateway (see [trac:TracOnWindowsIisWfastcgi])
    86  * a CGI-capable web server (see TracCgi), but //usage of Trac as a cgi script
    87    is highly discouraged//, better use one of the previous options.
     97 * a CGI-capable web server (see TracCgi), '''but usage of Trac as a cgi script
     98   is highly discouraged''', better use one of the previous options.
    8899   
    89 ==== Other Python Packages
    90 
    91  * [http://babel.edgewall.org Babel], version 0.9.5, 0.9.6 or >= 1.3
    92    needed for localization support
     100
     101==== Other Python Packages ====
     102
     103 * [http://babel.edgewall.org Babel], version >= 0.9.5,
     104   needed for localization support (unreleased version 1.0dev should work as well)
    93105 * [http://docutils.sourceforge.net/ docutils], version >= 0.3.9
    94106   for WikiRestructuredText.
    95  * [http://pygments.org Pygments] for
    96    [TracSyntaxColoring syntax highlighting].
     107 * [http://pygments.pocoo.org Pygments] for
     108   [wiki:TracSyntaxColoring syntax highlighting].
    97109   [http://silvercity.sourceforge.net/ SilverCity] and/or
    98110   [http://gnu.org/software/enscript/enscript.html Enscript] may still be used
     
    102114   an internal time zone implementation.
    103115
    104 {{{#!div style="border: 1pt dotted; margin: 1em"
    105 **Attention**: The available versions of these dependencies are not necessarily interchangeable, so please pay attention to the version numbers. If you are having trouble getting Trac to work, please double-check all the dependencies before asking for help on the [trac:MailingList] or [trac:IrcChannel].
    106 }}}
    107 
    108 Please refer to the documentation of these packages to find out how they are best installed. In addition, most of the [trac:TracInstallPlatforms platform-specific instructions] also describe the installation of the dependencies. Keep in mind however that the information there probably concern older versions of Trac than the one you're installing.
    109 
    110 == Installing Trac
    111 
    112 The [TracAdmin trac-admin] command-line tool, used to create and maintain [TracEnvironment project environments], as well as the [TracStandalone tracd] standalone server are installed along with Trac. There are several methods for installing Trac.
    113 
    114 It is assumed throughout this guide that you have elevated permissions as the `root` user, or by prefixing commands with `sudo`. The umask `0022` should be used for a typical installation on a Unix-based platform.
    115 
     116'''Attention''': The various available versions of these dependencies are not necessarily interchangable, so please pay attention to the version numbers above. If you are having trouble getting Trac to work please double-check all the dependencies before asking for help on the [trac:MailingList] or [trac:IrcChannel].
     117
     118Please refer to the documentation of these packages to find out how they are best installed. In addition, most of the [trac:TracInstallPlatforms platform-specific instructions] also describe the installation of the dependencies. Keep in mind however that the information there ''probably concern older versions of Trac than the one you're installing'' (there are even some pages that are still talking about Trac 0.8!).
     119
     120
     121== Installing Trac ==
    116122=== Using `easy_install`
    117 
    118 Trac can be installed from [https://pypi.python.org/pypi/Trac PyPI] or the Subversion repository using [http://pypi.python.org/pypi/setuptools setuptools].
    119 
    120 A few command-line examples:
    121 
    122  - Install Trac 1.0:
    123  {{{#!sh
    124 $ easy_install Trac==1.0
    125 }}}
    126  - Install latest development version:
    127  {{{#!sh
    128 $ easy_install Trac==dev
    129 }}}
     123One way to install Trac is using [http://pypi.python.org/pypi/setuptools setuptools].
     124With setuptools you can install Trac from the subversion repository;
     125
     126A few examples:
     127
     128 - install Trac 1.0:
     129   {{{
     130   easy_install Trac==1.0
     131   }}}
     132   (NOT YET ENABLED)
     133 - install latest development version 1.0dev:
     134   {{{
     135   easy_install Trac==dev
     136   }}}
    130137   Note that in this case you won't have the possibility to run a localized version of Trac;
    131    either use a released version or install from source.
    132 
    133 More information can be found on the [trac:wiki:setuptools setuptools] page.
    134 
    135 {{{#!div style="border: 1pt dotted; margin: 1em"
    136 **Setuptools Warning:** If the version of your setuptools is in the range 5.4 through 5.6, the environment variable `PKG_RESOURCES_CACHE_ZIP_MANIFESTS` must be set in order to avoid significant performance degradation. More information may be found in the sections on [#RunningtheStandaloneServer Running The Standalone Server] and [#RunningTraconaWebServer Running Trac on a Web Server].
    137 }}}
     138   either use a released version or install from source
    138139
    139140=== Using `pip`
    140 
    141 'pip' is an easy_install replacement that is very useful to quickly install Python packages.
    142 To get a Trac installation up and running in less than 5 minutes:
    143 
    144 Assuming you want to have your entire pip installation in `/opt/user/trac`:
     141'pip' is an easy_install replacement that is very useful to quickly install python packages.
     142To get a trac installation up and running in less than 5 minutes:
     143
     144Assuming you want to have your entire pip installation in `/opt/user/trac`
    145145
    146146 -
    147  {{{#!sh
    148 $ pip install trac psycopg2
    149 }}}
    150 or:
     147{{{
     148pip -E /opt/user/trac install trac psycopg2
     149}}}
     150or
    151151 -
    152  {{{#!sh
    153 $ pip install trac mysql-python
    154 }}}
    155 
    156 Make sure your OS specific headers are available for pip to automatically build PostgreSQL (`libpq-dev`) or MySQL (`libmysqlclient-dev`) bindings.
    157 
    158 pip will automatically resolve all dependencies (like Genshi, pygments, etc.), download the latest packages from pypi.python.org and create a self contained installation in `/opt/user/trac`.
    159 
    160 All commands (`tracd`, `trac-admin`) are available in `/opt/user/trac/bin`. This can also be leveraged for `mod_python` (using `PythonHandler` directive) and `mod_wsgi` (using `WSGIDaemonProcess` directive).
    161 
    162 Additionally, you can install several Trac plugins (listed [https://pypi.python.org/pypi?:action=browse&show=all&c=516 here]) through pip.
     152{{{
     153pip -E /opt/user/trac install trac mysql-python
     154}}}
     155
     156Make sure your OS specific headers are available for pip to automatically build PostgreSQL (libpq-dev) or MySQL (libmysqlclient-dev) bindings.
     157
     158pip will automatically resolve all dependencies (like Genshi, pygments, etc.) and download the latest packages on pypi.python.org and create a self contained installation in `/opt/user/trac`.
     159
     160All commands (`tracd`, `trac-admin`) are available in `/opt/user/trac/bin`. This can also be leveraged for `mod_python` (using `PythonHandler` directive) and `mod_wsgi` (using `WSGIDaemonProcess` directive)
     161
     162Additionally, you can install several trac plugins (listed [http://pypi.python.org/pypi?:action=search&term=trac&submit=search here]) through pip.
     163
     164
    163165
    164166=== From source
    165 
    166 Using the python-typical setup at the top of the source directory also works. You can obtain the source for a .tar.gz or .zip file corresponding to a release (e.g. `Trac-1.0.tar.gz`) from the [trac:TracDownload] page, or you can get the source directly from the repository. See [trac:TracRepositories#OfficialSubversionrepository TracRepositories] for details.
    167 
    168 {{{#!sh
     167Of course, using the python-typical setup at the top of the source directory also works.
     168
     169You can obtain the source for a .tar.gz or .zip file corresponding to a release (e.g. Trac-1.0.tar.gz), or you can get the source directly from the repository (see Trac:SubversionRepository for details).
     170
     171{{{
    169172$ python ./setup.py install
    170173}}}
    171174
    172 You will need root permissions or equivalent for this step.
    173 
    174 This will byte-compile the Python source code and install it as an .egg file or folder in the `site-packages` directory
    175 of your Python installation. The .egg will also contain all other resources needed by standard Trac, such as `htdocs` and `templates`.
    176 
    177 If you install from source and want to make Trac available in other languages, make sure Babel is installed. Only then, perform the `install` (or simply redo the `install` once again afterwards if you realize Babel was not yet installed):
    178 {{{#!sh
     175''You'll need root permissions or equivalent for this step.''
     176
     177This will byte-compile the python source code and install it as an .egg file or folder in the `site-packages` directory
     178of your Python installation. The .egg will also contain all other resources needed by standard Trac, such as htdocs and templates.
     179
     180The script will also install the [wiki:TracAdmin trac-admin] command-line tool, used to create and maintain [wiki:TracEnvironment project environments], as well as the [wiki:TracStandalone tracd] standalone server.
     181
     182If you install from source and want to make Trac available in other languages, make sure  Babel is installed. Only then, perform the `install` (or simply redo the `install` once again afterwards if you realize Babel was not yet installed):
     183{{{
    179184$ python ./setup.py install
    180185}}}
    181 
    182 Alternatively, you can run `bdist_egg` and copy the .egg from `dist/` to the place of your choice, or you can create a Windows installer (`bdist_wininst`).
    183 
    184 === Using installer
    185 
    186 On Windows Trac can be installed using the exe installers available on the [trac:TracDownload] page. Installers are available for the 32 and 64 bit versions of Python. Make sure to use the installer that matches the architecture of your Python installation.
    187 
    188 === Using package manager
    189 
    190 Trac may be available in the package repository for your platform. Note however, that the version provided by the package manager may not be the latest release.
    191 
    192 === Advanced `easy_install` Options
     186Alternatively, you can do a `bdist_egg` and copy the .egg from dist/ to the place of your choice, or you can create a Windows installer (`bdist_wininst`).
     187
     188=== Advanced Options ===
    193189
    194190To install Trac to a custom location, or find out about other advanced installation options, run:
    195 {{{#!sh
    196 $ easy_install --help
    197 }}}
    198 
    199 Also see [http://docs.python.org/2/install/index.html Installing Python Modules] for detailed information.
     191{{{
     192easy_install --help
     193}}}
     194
     195Also see [http://docs.python.org/inst/inst.html Installing Python Modules] for detailed information.
    200196
    201197Specifically, you might be interested in:
    202 {{{#!sh
    203 $ easy_install --prefix=/path/to/installdir
    204 }}}
    205 
    206 or, if installing Trac on a Mac OS X system:
    207 {{{#!sh
    208 $ easy_install --prefix=/usr/local --install-dir=/Library/Python/2.5/site-packages
    209 }}}
    210 
    211 '''Note''': If installing on Mac OS X 10.6 running {{{ easy_install http://svn.edgewall.org/repos/trac/trunk }}} will install into {{{ /usr/local }}} and {{{ /Library/Python/2.5/site-packages }}} by default.
     198{{{
     199easy_install --prefix=/path/to/installdir
     200}}}
     201or, if installing Trac to a Mac OS X system:
     202{{{
     203easy_install --prefix=/usr/local --install-dir=/Library/Python/2.5/site-packages
     204}}}
     205Note: If installing on Mac OS X 10.6 running {{{ easy_install http://svn.edgewall.org/repos/trac/trunk }}} will install into {{{ /usr/local }}} and {{{ /Library/Python/2.6/site-packages }}} by default
    212206
    213207The above will place your `tracd` and `trac-admin` commands into `/usr/local/bin` and will install the Trac libraries and dependencies into `/Library/Python/2.5/site-packages`, which is Apple's preferred location for third-party Python application installations.
    214208
    215 == Creating a Project Environment
    216 
    217 A [TracEnvironment Trac environment] is the backend where Trac stores information like wiki pages, tickets, reports, settings, etc. An environment is basically a directory that contains a human-readable [TracIni configuration file], and other files and directories.
    218 
    219 A new environment is created using [TracAdmin trac-admin]:
    220 {{{#!sh
     209
     210== Creating a Project Environment ==
     211
     212A [TracEnvironment Trac environment] is the backend storage where Trac stores information like wiki pages, tickets, reports, settings, etc. An environment is basically a directory that contains a human-readable [TracIni configuration file], and various other files and directories.
     213
     214A new environment is created using [wiki:TracAdmin trac-admin]:
     215{{{
    221216$ trac-admin /path/to/myproject initenv
    222217}}}
     
    225220
    226221Using the default database connection string in particular will always work as long as you have SQLite installed.
    227 For the other [trac:DatabaseBackend database backends] you should plan ahead and already have a database ready to use at this point.
    228 
    229 Since 0.12, Trac doesn't ask for a [TracEnvironment#SourceCodeRepository source code repository] anymore when creating an environment. Repositories can be [TracRepositoryAdmin added] afterwards, and support for specific version control systems is disabled by default.
     222For the other [DatabaseBackend database backends] you should plan ahead and already have a database ready to use at this point.
     223
     224Since 0.12, Trac doesn't ask for a [TracEnvironment#SourceCodeRepository source code repository] anymore when creating an environment. Repositories can be [TracRepositoryAdmin added] afterward, or the version control support can be disabled completely if you don't need it.
    230225
    231226Also note that the values you specify here can be changed later by directly editing the [TracIni conf/trac.ini] configuration file.
    232227
    233 {{{#!div style="border: 1pt dotted; margin: 1em"
    234 **Filesystem Warning:** When selecting the location of your environment, make sure that the filesystem on which the environment directory resides supports sub-second timestamps (i.e. **not** `ext2` or `ext3` on Linux, or HFS+ on OSX), as the modification time of the `conf/trac.ini` file will be monitored to decide whether an environment restart is needed or not. A too coarse-grained timestamp resolution may result in inconsistencies in Trac < 1.0.2. The best advice is to opt for a platform with sub-second timestamp resolution, regardless of the Trac version.
    235 }}}
    236 
    237228Finally, make sure the user account under which the web front-end runs will have '''write permissions''' to the environment directory and all the files inside. This will be the case if you run `trac-admin ... initenv` as this user. If not, you should set the correct user afterwards. For example on Linux, with the web server running as user `apache` and group `apache`, enter:
    238 {{{#!sh
    239 $ chown -R apache.apache /path/to/myproject
    240 }}}
    241 
    242 The actual username and groupname of the Apache server may not be exactly `apache`, and are specified in the Apache configuration file by the directives `User` and `Group` (if Apache `httpd` is what you use).
     229{{{
     230# chown -R apache.apache /path/to/myproject
     231}}}
    243232
    244233{{{#!div class=important
     
    246235}}}
    247236
     237
    248238== Deploying Trac
    249239
    250 === Running the Standalone Server
    251 
    252 After having created a Trac environment, you can easily try the web interface by running the standalone server [TracStandalone tracd]:
    253 {{{#!sh
     240=== Running the Standalone Server ===
     241
     242After having created a Trac environment, you can easily try the web interface by running the standalone server [wiki:TracStandalone tracd]:
     243{{{
    254244$ tracd --port 8000 /path/to/myproject
    255245}}}
    256246
    257247Then, fire up a browser and visit `http://localhost:8000/`. You should get a simple listing of all environments that `tracd` knows about. Follow the link to the environment you just created, and you should see Trac in action. If you only plan on managing a single project with Trac you can have the standalone server skip the environment list by starting it like this:
    258 {{{#!sh
     248{{{
    259249$ tracd -s --port 8000 /path/to/myproject
    260250}}}
    261251
    262 {{{#!div style="border: 1pt dotted; margin: 1em"
    263 **Setuptools Warning:** If the version of your setuptools is in the range 5.4 through 5.6, the environment variable `PKG_RESOURCES_CACHE_ZIP_MANIFESTS` must be set in order to avoid significant performance degradation. The environment variable can be set system-wide, or for just the user that runs the `tracd` process. There are several ways to accomplish this in addition to what is discussed here, and depending on the distribution of your OS.
    264 
    265 To be effective system-wide a shell script with the `export` statement may be added to `/etc/profile.d`.  !Ubuntu/Debian users can add the `export` statement to `/etc/apache2/envvars`. !RedHat/CentOS/Fedora users can add the `export` statement to `/etc/sysconfig/httpd`. To be effective for a user session the `export` statement may be added to `~/.profile`.
    266 {{{#!sh
    267 export PKG_RESOURCES_CACHE_ZIP_MANIFESTS=1
    268 }}}
    269 
    270 Alternatively, the variable can be set in the shell before executing `tracd`:
    271 {{{#!sh
    272 $ PKG_RESOURCES_CACHE_ZIP_MANIFESTS=1 tracd --port 8000 /path/to/myproject
    273 }}}
    274 }}}
    275 
    276 === Running Trac on a Web Server
     252=== Running Trac on a Web Server ===
    277253
    278254Trac provides various options for connecting to a "real" web server:
    279  - [TracFastCgi FastCGI]
     255 - [wiki:TracFastCgi FastCGI]
    280256 - [wiki:TracModWSGI mod_wsgi]
    281  - [TracModPython mod_python]
    282  - //[TracCgi CGI]: should not be used, as it degrades performance//
     257 - //[wiki:TracModPython mod_python] (no longer recommended, as mod_python is not actively maintained anymore)//
     258 - //[wiki:TracCgi CGI] (should not be used, as the performance is far from optimal)//
    283259
    284260Trac also supports [trac:TracOnWindowsIisAjp AJP] which may be your choice if you want to connect to IIS. Other deployment scenarios are possible: [trac:TracNginxRecipe nginx], [http://projects.unbit.it/uwsgi/wiki/Example#Traconapacheinasub-uri uwsgi], [trac:TracOnWindowsIisIsapi Isapi-wsgi] etc.
    285261
    286 ==== Generating the Trac cgi-bin directory #cgi-bin
    287 
    288 In order for Trac to function properly with FastCGI you need to have a `trac.fcgi` file and for mod_wsgi a `trac.wsgi` file. These are Python scripts which load the appropriate Python code. They can be generated using the `deploy` option of [TracAdmin trac-admin].
    289 
    290 There is, however, a bit of a chicken-and-egg problem. The [TracAdmin trac-admin] command requires an existing environment to function, but complains if the deploy directory already exists. This is a problem, because environments are often stored in a subdirectory of the deploy. The solution is to do something like this:
    291 {{{#!sh
    292 $ mkdir -p /usr/share/trac/projects/my-project
    293 $ trac-admin /usr/share/trac/projects/my-project initenv
    294 $ trac-admin /usr/share/trac/projects/my-project deploy /tmp/deploy
    295 $ mv /tmp/deploy/* /usr/share/trac
    296 }}}
    297 
    298 Don't forget to check that the web server has the execution right on scripts in the `/usr/share/trac/cgi-bin` directory.
    299 
    300 ==== Mapping Static Resources
    301 
    302 Out of the box, Trac will pass static resources such as style sheets or images through itself. For anything but a tracd only based deployment, this is far from optimal as the web server could be set up to directly serve those static resources. For CGI setup, this is '''highly undesirable''' as it causes abysmal performance.
    303 
    304 Web servers such as [http://httpd.apache.org/ Apache] allow you to create "Aliases" to resources, giving them a virtual URL that doesn't necessarily reflect the layout of the servers file system. We also can map requests for static resources directly to the directory on the file system, avoiding processing these requests by Trac itself.
     262==== Generating the Trac cgi-bin directory ==== #cgi-bin
     263
     264In order for Trac to function properly with FastCGI you need to have a `trac.fcgi` file and for mod_wsgi a `trac.wsgi` file. These are Python scripts which load the appropriate Python code. They can be generated using the `deploy` option of [wiki:TracAdmin trac-admin].
     265
     266There is, however, a bit of a chicken-and-egg problem. The [wiki:TracAdmin trac-admin] command requires an existing environment to function, but complains if the deploy directory already exists. This is a problem, because environments are often stored in a subdirectory of the deploy. The solution is to do something like this:
     267{{{
     268mkdir -p /usr/share/trac/projects/my-project
     269trac-admin /usr/share/trac/projects/my-project initenv
     270trac-admin /usr/share/trac/projects/my-project deploy /tmp/deploy
     271mv /tmp/deploy/* /usr/share/trac
     272}}}
     273
     274
     275==== Mapping Static Resources ====
     276
     277Out of the box, Trac will pass static resources such as style sheets or images through itself. For anything but a tracd only based deployment, this is far from optimal as the web server could be set up to directly serve those static resources (for CGI setup, this is '''highly undesirable''' and will cause abysmal performance).
     278
     279Web servers such as [http://httpd.apache.org/ Apache] allow you to create “Aliases” to resources, giving them a virtual URL that doesn't necessarily reflect the layout of the servers file system. We also can map requests for static resources directly to the directory on the file system, avoiding processing these requests by Trac itself.
    305280
    306281There are two primary URL paths for static resources - `/chrome/common` and `/chrome/site`. Plugins can add their own resources, usually accessible by `/chrome/<plugin>` path, so its important to override only known paths and not try to make universal `/chrome` alias for everything.
     
    314289 - `<plugins>/` - one directory for each resource directory managed by the plugins enabled for this environment
    315290
    316 ===== Example: Apache and `ScriptAlias` #ScriptAlias-example
     291===== Example: Apache and `ScriptAlias` ===== #ScriptAlias-example
    317292
    318293Assuming the deployment has been done this way:
    319 {{{#!sh
    320 $ trac-admin /var/trac/env deploy /path/to/shared/trac
     294{{{
     295$ trac-admin /var/trac/env deploy /path/to/trac/htdocs/common
    321296}}}
    322297
    323298Add the following snippet to Apache configuration ''before'' the `ScriptAlias` or `WSGIScriptAlias` (which map all the other requests to the Trac application), changing paths to match your deployment:
    324 {{{#!apache
     299{{{
    325300Alias /trac/chrome/common /path/to/trac/htdocs/common
    326301Alias /trac/chrome/site /path/to/trac/htdocs/site
     
    332307}}}
    333308
    334 If using mod_python, you might want to add this too, otherwise the alias will be ignored:
    335 {{{#!apache
     309If using mod_python, you might want to add this too (otherwise, the alias will be ignored):
     310{{{
    336311<Location "/trac/chrome/common/">
    337312  SetHandler None
     
    342317
    343318Similarly, if you have static resources in a project's `htdocs` directory (which is referenced by `/trac/chrome/site` URL in themes), you can configure Apache to serve those resources (again, put this ''before'' the `ScriptAlias` or `WSGIScriptAlias` for the .*cgi scripts, and adjust names and locations to match your installation):
    344 {{{#!apache
     319{{{
    345320Alias /trac/chrome/site /path/to/projectenv/htdocs
    346321
     
    351326}}}
    352327
    353 Alternatively to aliasing `/trac/chrome/common`, you can tell Trac to generate direct links for those static resources (and only those), using the [[TracIni#trac-section| [trac] htdocs_location]] configuration setting:
    354 {{{#!ini
     328Alternatively to aliasing `/trac/chrome/common`, you can tell Trac to generate direct links for those static resources (and only those), using the [[wiki:TracIni#trac-section| [trac] htdocs_location]] configuration setting:
     329{{{
    355330[trac]
    356331htdocs_location = http://static.example.org/trac-common/
    357332}}}
    358 
    359 Note that this makes it easy to have a dedicated domain serve those static resources, preferentially [http://code.google.com/speed/page-speed/docs/request.html#ServeFromCookielessDomain cookie-less].
     333Note that this makes it easy to have a dedicated domain serve those static resources (preferentially [http://code.google.com/speed/page-speed/docs/request.html#ServeFromCookielessDomain cookie-less]).
    360334
    361335Of course, you still need to make the Trac `htdocs/common` directory available through the web server at the specified URL, for example by copying (or linking) the directory into the document root of the web server:
    362 {{{#!sh
     336{{{
    363337$ ln -s /path/to/trac/htdocs/common /var/www/static.example.org/trac-common
    364338}}}
    365339
    366 ==== Setting up the Plugin Cache
    367 
    368 Some Python plugins need to be extracted to a cache directory. By default the cache resides in the home directory of the current user. When running Trac on a Web Server as a dedicated user (which is highly recommended) who has no home directory, this might prevent the plugins from starting. To override the cache location you can set the `PYTHON_EGG_CACHE` environment variable. Refer to your server documentation for detailed instructions on how to set environment variables.
    369 
    370 == Configuring Authentication
    371 
    372 Trac uses HTTP authentication. You'll need to configure your webserver to request authentication when the `.../login` URL is hit (the virtual path of the "login" button). Trac will automatically pick the `REMOTE_USER` variable up after you provide your credentials. Therefore, all user management goes through your web server configuration. Please consult the documentation of your web server for more info.
     340
     341==== Setting up the Plugin Cache ====
     342
     343Some Python plugins need to be extracted to a cache directory. By default the cache resides in the home directory of the current user. When running Trac on a Web Server as a dedicated user (which is highly recommended) who has no home directory, this might prevent the plugins from starting. To override the cache location you can set the PYTHON_EGG_CACHE environment variable. Refer to your server documentation for detailed instructions on how to set environment variables.
     344
     345== Configuring Authentication ==
     346
     347Trac uses HTTP authentication. You'll need to configure your webserver to request authentication when the `.../login` URL is hit (the virtual path of the "login" button). Trac will automatically pick the REMOTE_USER variable up after you provide your credentials. Therefore, all user management goes through your web server configuration. Please consult the documentation of your web server for more info.
    373348
    374349The process of adding, removing, and configuring user accounts for authentication depends on the specific way you run Trac.
     
    377352 * TracStandalone#UsingAuthentication if you use the standalone server, `tracd`.
    378353 * [wiki:TracModWSGI#ConfiguringAuthentication TracModWSGI#ConfiguringAuthentication] if you use the Apache web server, with any of its front end: `mod_wsgi` of course, but the same instructions applies also for `mod_python`, `mod_fcgi` or `mod_fastcgi`.
    379  * TracFastCgi if you are using another web server with FCGI support, such as Cherokee, Lighttpd, !LiteSpeed, nginx.
    380 
    381 The following document also contains some useful information for beginners: [trac:TracAuthenticationIntroduction].
     354 * TracFastCgi if you're using another web server with FCGI support (Cherokee, Lighttpd, !LiteSpeed, nginx)
    382355
    383356== Granting admin rights to the admin user
    384 
    385357Grant admin rights to user admin:
    386 {{{#!sh
     358{{{
    387359$ trac-admin /path/to/myproject permission add admin TRAC_ADMIN
    388360}}}
    389 
    390 This user will have an "Admin" entry menu that will allow you to administrate your Trac project.
     361This user will have an "Admin" entry menu that will allow you to admin your trac project.
    391362
    392363== Finishing the install
    393364
    394 === Enable version control components
    395 
    396 Support for version control systems is provided by optional components in Trac and the components are disabled by default //(since 1.0)//. Subversion and Git must be explicitly enabled if you wish to use them. See TracRepositoryAdmin for more details.
    397 
    398 The version control systems are enabled by adding the following to the `[components]` section of your [TracIni#components-section trac.ini], or enabling the components in the "Plugins" admin panel:
    399 
    400 {{{#!ini
    401 [components]
    402 tracopt.versioncontrol.svn.* = enabled
    403 }}}
    404 
    405 {{{#!ini
    406 [components]
    407 tracopt.versioncontrol.git.* = enabled
    408 }}}
    409 
    410 After enabling the components, repositories can be configured through the //Repositories// admin panel or by editing [TracIni#repositories-section trac.ini]. Automatic changeset references can be inserted as ticket comments by configuring [TracRepositoryAdmin#Automaticchangesetreferencesintickets CommitTicketUpdater].
    411 
    412 === Using Trac
     365=== Automatic reference to the SVN changesets in Trac tickets ===
     366
     367You can configure SVN to automatically add a reference to the changeset into the ticket comments, whenever changes are committed to the repository. The description of the commit needs to contain one of the following formulas:
     368 * '''`Refs #123`''' - to reference this changeset in `#123` ticket
     369 * '''`Fixes #123`''' - to reference this changeset and close `#123` ticket with the default status ''fixed''
     370
     371This functionality requires a post-commit hook to be installed as described in [wiki:TracRepositoryAdmin#ExplicitSync TracRepositoryAdmin], and enabling the optional commit updater components by adding the following line to the `[components]` section of your [wiki:TracIni#components-section trac.ini], or enabling the components in the "Plugins" admin panel.
     372{{{
     373tracopt.ticket.commit_updater.* = enabled
     374}}}
     375For more information, see the documentation of the `CommitTicketUpdater` component in the "Plugins" admin panel.
     376
     377=== Using Trac ===
    413378
    414379Once you have your Trac site up and running, you should be able to create tickets, view the timeline, browse your version control repository if configured, etc.
    415380
    416 Keep in mind that //anonymous// (not logged in) users can by default access only a few of the features, in particular they will have a read-only access to the resources. You will need to configure authentication and grant additional [TracPermissions permissions] to authenticated users to see the full set of features.
     381Keep in mind that //anonymous// (not logged in) users can by default access only a few of the features, in particular they will have a read-only access to the resources. You will need to configure authentication and grant additional [wiki:TracPermissions permissions] to authenticated users to see the full set of features.
    417382
    418383'' Enjoy! ''