Edgewall Software

Changes between Version 21 and Version 22 of 0.12/TracInstall


Ignore:
Timestamp:
Jul 16, 2012, 9:16:11 PM (10 years ago)
Author:
trac
Comment:

Legend:

Unmodified
Added
Removed
Modified
  • 0.12/TracInstall

    v21 v22  
    1 ** Note: this page was used to prepare the 0.12 version of wiki:/TracInstall, see now directly that toplevel page **
    2 = Trac Installation Guide for 0.12dev =
    3 {{{
    4 #!div style="margin-top: .5em; padding: 0 1em; background-color: #ffd; border:1px outset #ddc;"
    5 
    6   '''NOTE: this page is for 0.12dev (trunk), the version currently in development. For installing previous Trac versions, please refer to [[0.11/TracInstall]]'''
    7 }}}
     1{{{
     2#!div style="margin-top: .5em; padding: 0 1em; background-color: #ffd; border:1px outset #ddc; text-align: center"
     3
     4  '''NOTE: this page is for 0.12, the current version. \\
     5  For installing previous Trac versions, please refer to [[0.11/TracInstall]]; the installations notes for the next version of Trac are available in [[0.13/TracInstall]]'''
     6}}}
     7= Trac Installation Guide for 0.12 =
    88[[TracGuideToc]]
     9[[TranslatedPages]]
    910
    1011Trac 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.
    1112
    12 Since 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.
    13 
    14 If you're interested in contributing new translations for other languages or enhance the existing translations, then please have a look at ["TracL10N"].
    15 
    16 What 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 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.
    17 
     13Since 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 **first** have installed the optional package [#OtherPythonPackages Babel]. Lacking Babel, you will only get the default English version, as usual. If you install Babel later on, you will need to re-install Trac.
     14
     15If you're interested in contributing new translations for other languages or enhance the existing translations, then please have a look at [trac:wiki:TracL10N TracL10N].
     16
     17What 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:wiki: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.
     18
     19[[PageOutline(2-3,Installation Steps,inline)]]
    1820
    1921== Dependencies ==
     
    2224
    2325 * [http://www.python.org/ Python], version >= 2.4 and < 3.0
    24    (note that we dropped the support for Python 2.3 in this release)
     26   //(note that we dropped the support for Python 2.3 in this release and that this will be the last Trac release supporting Python 2.4)//
    2527 * [http://peak.telecommunity.com/DevCenter/setuptools setuptools], version >= 0.6
    26  * [http://genshi.edgewall.org/wiki/Download Genshi], [genshi:source:trunk trunk], from svn, minimum required revision is [G1072], current [G1092] works fine as well.
     28 * [http://genshi.edgewall.org/wiki/Download Genshi], version >= 0.6 (but < 0.7dev, i.e. don't use Genshi trunk)
    2729
    2830You also need a database system and the corresponding python bindings.
     
    3436
    3537If you're using Python 2.4 and need pysqlite, you can download from
    36 [http://code.google.com/p/pysqlite/downloads/list google code] the Windows
    37 installers or the tar.gz archive for building from source:
     38[http://code.google.com/p/pysqlite/downloads/list google code] the Windows installers or the tar.gz archive for building from source:
    3839{{{
    3940$ tar xvfz <version>.tar.gz
     
    4445This will extract the SQLite code and build the bindings.
    4546
    46 SQLite 2.x is no longer supported. For SQLite 3.x, the pysqlite 1.1.x
    47 bindings are also no longer supported, use pysqlite 2.x.
    48 
    49 See additional information in [trac:PySqlite PySqlite].
     47To install SQLite, your system may require the development headers. Without these you will get various GCC related errors when attempting to build:
     48
     49{{{
     50$ apt-get install libsqlite3-dev
     51}}}
     52
     53SQLite 2.x is no longer supported, and neither is !PySqlite 1.1.x.
     54
     55A known bug !PySqlite versions 2.5.2-4 prohibits upgrade of trac databases
     56from 0.11.x to 0.12. Please use versions 2.5.5 and newer or 2.5.1 and
     57older. See [trac:#9434] for more detail.
     58
     59See additional information in [trac:PySqlite].
    5060
    5161==== For the PostgreSQL database #ForPostgreSQL
    5262
    5363You need to install the database and its Python bindings:
    54  * [http://www.postgresql.org/ PostgreSQL]
     64 * [http://www.postgresql.org/ PostgreSQL], version 8.0 or later
    5565 * [http://pypi.python.org/pypi/psycopg2 psycopg2]
    5666
     
    6575 * [http://sf.net/projects/mysql-python MySQLdb], version 1.2.2 or later
    6676
    67 It is '''very''' important to read carefully the  [trac:MySqlDb MySqlDb] page before creating the database.
     77It is '''very''' important to read carefully the  [trac:MySqlDb] page before creating the database.
    6878
    6979=== Optional Dependencies
     
    7282
    7383===== Subversion =====
    74  * [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.
    75 
    76 There are [http://subversion.apache.org/packages.html pre-compiled SWIG bindings] available for various platforms. Note that Trac '''doesn't''' use [http://pysvn.tigris.org/ PySVN], neither does it work yet with the newer `ctype`-style bindings
    77 
    78 
    79 '''Please note:''' if using Subversion, Trac must be installed on the '''same machine'''. Remote repositories are currently [trac:ticket:493 not supported].
     84
     85[http://subversion.apache.org/ Subversion] 1.5.x or 1.6.x and the '''''corresponding''''' Python bindings.
     86
     87There are [http://subversion.apache.org/packages.html pre-compiled SWIG bindings] available for various platforms. See also the TracSubversion page for details about Windows packages.
     88
     89Older versions starting from 1.4.0, etc. should still work. For troubleshooting information, check the [trac:TracSubversion#Troubleshooting TracSubversion] page. Versions prior to 1.4.0 won't probably work since trac uses svn core functionality (e.g. svn_path_canonicalize) that is not implemented in the python swig wrapper in svn <= 1.3.x (although it exists in the svn lib itself).
     90
     91Note that Trac '''doesn't''' use [http://pysvn.tigris.org/ PySVN], neither does it work yet with the newer `ctype`-style bindings.
     92
     93'''Please note:''' if using Subversion, Trac must be installed on the '''same machine'''. Remote repositories are currently [trac:#493 not supported].
    8094
    8195
    8296===== Others =====
    8397
    84 Support for other version control systems is provided via third-parties. See [trac:PluginList PluginList] and [trac:VersioningSystemBackend VersioningSystemBackend].
     98Support for other version control systems is provided via third-parties. See [trac:PluginList] and [trac:VersionControlSystem].
    8599
    86100==== Web Server ====
     
    89103Alternatively you configure Trac to run in any of the following environments.
    90104 * [http://httpd.apache.org/ Apache] with
    91    - [http://code.google.com/p/modwsgi/ mod_wsgi], see [wiki:TracModWSGI] and
    92      http://code.google.com/p/modwsgi/wiki/IntegrationWithTrac
    93    - [http://modpython.org/ mod_python 3.3.1], see TracModPython)
    94  * a [http://www.fastcgi.com/ FastCGI]-capable web server (see TracFastCgi)
    95  * an [http://tomcat.apache.org/connectors-doc/ajp/ajpv13a.html AJP]-capable web
    96    server (see [trac:TracOnWindowsIisAjp TracOnWindowsIisAjp])
    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 following options,
     105   - [http://code.google.com/p/modwsgi/ mod_wsgi], see [wiki:TracModWSGI] (preferred)
     106   - //[http://modpython.org/ mod_python 3.3.1], see TracModPython (deprecated)//
     107 * any [http://www.fastcgi.com/ FastCGI]-capable web server, see TracFastCgi
     108 * any [http://tomcat.apache.org/connectors-doc/ajp/ajpv13a.html AJP]-capable web
     109   server, see [trac:TracOnWindowsIisAjp]
     110 * IIS with [http://code.google.com/p/isapi-wsgi/ Isapi-wsgi], see [trac:TracOnWindowsIisIsapi]
     111 * //as a last resort, a CGI-capable web server (see TracCgi), but usage of Trac as a cgi script
     112   is highly discouraged, better use one of the previous options.//
    99113   
    100114
    101115==== Other Python Packages ====
    102116
    103  * [http://babel.edgewall.org Babel], version >= 0.9.5,
    104    needed for localization support
     117 * [http://babel.edgewall.org Babel], version 0.9.5,
     118   needed for localization support[[BR]]
     119   ''Note: '' If you want to be able to use the Trac interface in other languages, then make sure you first have installed the optional package Babel. Lacking Babel, you will only get the default english version, as usual. If you install Babel later on, you will need to re-install Trac.
    105120 * [http://docutils.sourceforge.net/ docutils], version >= 0.3.9
    106121   for WikiRestructuredText.
     
    114129   an internal time zone implementation.
    115130
    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 MailingList] or [trac:IrcChannel IrcChannel].
     131'''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].
    117132
    118133Please 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!).
     
    120135
    121136== Installing Trac ==
    122 
    123 One way to install Trac is using `setuptools`.
    124 With setuptools you can install Trac from the subversion repository; for example,
    125 to install release version 0.12dev do:
    126 {{{
    127 easy_install http://svn.edgewall.org/repos/trac/trunk
    128 }}}
    129 
    130 But of course the python-typical setup at the top of the source directory also works:
     137=== Using `easy_install`
     138One way to install Trac is using [http://pypi.python.org/pypi/setuptools setuptools].
     139With setuptools you can install Trac from the subversion repository;
     140
     141A few examples:
     142
     143 - first install of the latest stable version Trac 0.12.3, with i18n support:
     144   {{{
     145   easy_install Babel==0.9.5
     146   easy_install Trac
     147   }}}
     148   ''It's very important to run the two `easy_install` commands separately, otherwise the message catalogs won't be generated.''
     149
     150 - upgrade to the latest stable version of Trac:
     151   {{{
     152   easy_install -U Trac
     153   }}}
     154
     155 - upgrade to the latest trunk development version (0.13dev):
     156   {{{
     157   easy_install -U Trac==dev
     158   }}}
     159
     160For upgrades, reading the TracUpgrade page is mandatory, of course.
     161
     162=== From source
     163If you want more control, you can download the source in archive form, or do a checkout from one of the official [[Trac:TracRepositories|source code repositories]].
     164
     165Be sure to have the prerequisites already installed. You can also obtain the Genshi and Babel source packages from http://www.edgewall.org and follow for them a similar installation procedure, or you can just `easy_install` those, see [#Usingeasy_install above].
     166
     167Once you've unpacked the Trac archive or performed the checkout, move in the top-level folder and do:
    131168{{{
    132169$ python ./setup.py install
    133170}}}
    134 See SubversionRepository for details about getting the source.
    135 
    136 ''Note 1: you'll need root permissions or equivalent for this step.'' [[br]]
    137 ''Note 2: installing from source is the preferred method if you want to have a localized version of Trac'' [[br]]
     171
     172You'll need root permissions or equivalent for this step.
    138173
    139174This will byte-compile the python source code and install it as an .egg file or folder in the `site-packages` directory
     
    142177The 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.
    143178
    144 If you want to make Trac available in other languages, make sure you have installed Babel and then run this additional step before doing the `install` (or simply redo the `install` afterwards):
    145 {{{
    146 $ python ./setup.py compile_catalog -f
    147 }}}
    148 (the `-f` flag is needed as long as some translations are marked ''fuzzy'', i.e. incomplete, which will most probably be the case during the whole development period, as  strings are continuously added or modified)
    149 
     179If 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):
     180{{{
     181$ python ./setup.py install
     182}}}
     183Alternatively, 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`).
    150184
    151185=== Advanced Options ===
    152186
     187==== Custom location with `easy_install`
     188
    153189To install Trac to a custom location, or find out about other advanced installation options, run:
    154190{{{
     
    169205
    170206The 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.
     207
     208==== Using `pip`
     209'pip' is an easy_install replacement that is very useful to quickly install python packages.
     210To get a trac installation up and running in less than 5 minutes:
     211
     212Assuming you want to have your entire pip installation in /opt/user/trac:
     213
     214 -
     215{{{
     216pip -E /opt/user/trac install trac psycopg2
     217}}}
     218or
     219 -
     220{{{
     221pip -E /opt/user/trac install trac mysql-python
     222}}}
     223
     224Make sure your OS specific headers are available for pip to automatically build PostgreSQL (libpq-dev) or MySQL (libmysqlclient-dev) bindings.
     225
     226pip 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 .
     227
     228All 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)
     229
     230Additionally, you can install several trac plugins (listed [http://pypi.python.org/pypi?:action=search&term=trac&submit=search here]) through pip.
     231
    171232
    172233
     
    194255}}}
    195256
    196 == Running the Standalone Server ==
     257{{{#!div class=important
     258'''Warning:''' Please only use ASCII-characters for account name and project path, unicode characters are not supported there.
     259}}}
     260
     261
     262== Deploying Trac
     263
     264=== Running the Standalone Server ===
    197265
    198266After having created a Trac environment, you can easily try the web interface by running the standalone server [wiki:TracStandalone tracd]:
     
    206274}}}
    207275
    208 == Running Trac on a Web Server ==
    209 
    210 Trac provides various options for connecting to a "real" web server: [wiki:TracCgi CGI], [wiki:TracFastCgi FastCGI], [wiki:TracModWSGI mod_wsgi] and [wiki:TracModPython mod_python]. For decent performance, it is recommended that you use either FastCGI or mod_wsgi.
    211 
    212 Trac also supports [trac:TracOnWindowsIisAjp AJP] which may be your choice if you want to connect to IIS.
    213 
    214 ==== Generating the Trac cgi-bin directory ====
     276=== Running Trac on a Web Server ===
     277
     278Trac provides various options for connecting to a "real" web server:
     279 - [wiki:TracFastCgi FastCGI]
     280 - [wiki:TracModWSGI mod_wsgi]
     281 - //[wiki:TracModPython mod_python] (no longer recommended, as mod_python is not actively maintained anymore)//
     282 - //[wiki:TracCgi CGI] (should not be used, as the performance is far from optimal)//
     283
     284Trac 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.
     285
     286==== Generating the Trac cgi-bin directory ==== #cgi-bin
    215287
    216288In 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].
     
    224296}}}
    225297
     298
     299==== Mapping Static Resources ====
     300
     301Out 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).
     302
     303Web 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.
     304
     305There 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.
     306
     307Note that in order to get those static resources on the filesystem, you need first to extract the relevant resources from Trac using the [TracAdmin trac-admin]` <environment> deploy` command:
     308[[TracAdminHelp(deploy)]]
     309
     310The target `<directory>` will then contain an `htdocs` directory with:
     311 - `site/` - a copy of the environment's directory `htdocs/`
     312 - `common/` - the static resources of Trac itself
     313 - `<plugins>/` - one directory for each resource directory managed by the plugins enabled for this environment
     314
     315===== Example: Apache and `ScriptAlias` ===== #ScriptAlias-example
     316
     317Assuming the deployment has been done this way:
     318{{{
     319$ trac-admin /var/trac/env deploy /path/to/trac/htdocs/common
     320}}}
     321
     322Add 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:
     323{{{
     324Alias /trac/chrome/common /path/to/trac/htdocs/common
     325Alias /trac/chrome/site /path/to/trac/htdocs/site
     326
     327<Directory "/path/to/www/trac/htdocs">
     328  Order allow,deny
     329  Allow from all
     330</Directory>
     331}}}
     332
     333If using mod_python, you might want to add this too (otherwise, the alias will be ignored):
     334{{{
     335<Location "/trac/chrome/common/">
     336  SetHandler None
     337</Location>
     338}}}
     339
     340Note that we mapped `/trac` part of the URL to the `trac.*cgi` script, and the path `/trac/chrome/common` is the path you have to append to that location to intercept requests to the static resources.
     341
     342Similarly, 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):
     343{{{
     344Alias /trac/chrome/site /path/to/projectenv/htdocs
     345
     346<Directory "/path/to/projectenv/htdocs">
     347  Order allow,deny
     348  Allow from all
     349</Directory>
     350}}}
     351
     352Alternatively 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:
     353{{{
     354[trac]
     355htdocs_location = http://static.example.org/trac-common/
     356}}}
     357Note 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]).
     358
     359Of 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:
     360{{{
     361$ ln -s /path/to/trac/htdocs/common /var/www/static.example.org/trac-common
     362}}}
     363
     364
    226365==== Setting up the Plugin Cache ====
    227366
     
    230369== Configuring Authentication ==
    231370
    232 The process of adding, removing, and configuring user accounts for authentication depends on the specific way you run Trac. The basic procedure is described in the [wiki:TracCgi#AddingAuthentication "Adding Authentication"] section on the TracCgi page. To learn how to setup authentication for the frontend you're using, please refer to one of the following pages:
    233 
    234  * TracStandalone if you use the standalone server, `tracd`.
    235  * TracCgi if you use the CGI or FastCGI web front ends.
    236  * [wiki:TracModWSGI] if you use the Apache mod_wsgi web front end.
    237  * TracModPython if you use the Apache mod_python web front end.
    238 
    239 
    240 == Automatic reference to the SVN changesets in Trac tickets ==
     371Trac 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.
     372
     373The process of adding, removing, and configuring user accounts for authentication depends on the specific way you run Trac.
     374
     375Please refer to one of the following sections:
     376 * TracStandalone#UsingAuthentication if you use the standalone server, `tracd`.
     377 * [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`.
     378 * TracFastCgi if you're using another web server with FCGI support (Cherokee, Lighttpd, !LiteSpeed, nginx)
     379
     380== Granting admin rights to the admin user
     381Grant admin rights to user admin:
     382{{{
     383$ trac-admin /path/to/myproject permission add admin TRAC_ADMIN
     384}}}
     385This user will have an "Admin" entry menu that will allow you to admin your trac project.
     386
     387== Finishing the install
     388
     389=== Automatic reference to the SVN changesets in Trac tickets ===
    241390
    242391You 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:
     
    250399For more information, see the documentation of the `CommitTicketUpdater` component in the "Plugins" admin panel.
    251400
    252 == Using Trac ==
     401=== Using Trac ===
    253402
    254403Once 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.
    255404
    256 Keep in mind that anonymous (not logged in) users can by default access most but not all of the features. You will need to configure authentication and grant additional [wiki:TracPermissions permissions] to authenticated users to see the full set of features.
     405Keep 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.
    257406
    258407'' Enjoy! ''
     
    261410
    262411----
    263 See also: [trac:TracInstallPlatforms TracInstallPlatforms], TracGuide, TracCgi, TracFastCgi, TracModPython, [wiki:TracModWSGI], TracUpgrade, TracPermissions
     412See also: [trac:TracInstallPlatforms TracInstallPlatforms], TracGuide, TracUpgrade, TracPermissions