Changes between Version 2 and Version 3 of TracInstall


Ignore:
Timestamp:
12/10/15 08:08:01 (2 years ago)
Author:
trac
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • TracInstall

    v2 v3  
    44Trac 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. 
    55 
    6 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. 
    7  
    8 If you're interested in contributing new translations for other languages or enhance the existing translations, then please have a look at [[trac:TracL10N]]. 
    9  
    10 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. 
     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 **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. 
     7 
     8If 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]. 
     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: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. 
    1111 
    1212[[PageOutline(2-3,Installation Steps,inline)]] 
     
    1717 
    1818 * [http://www.python.org/ Python], version >= 2.4 and < 3.0 
    19    (note that we dropped the support for Python 2.3 in this release) 
     19   //(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)// 
    2020 * [http://peak.telecommunity.com/DevCenter/setuptools setuptools], version >= 0.6 
    21  * [http://genshi.edgewall.org/wiki/Download Genshi], version >= 0.6 
     21 * [http://genshi.edgewall.org/wiki/Download Genshi], version >= 0.6 (but < 0.7dev, i.e. don't use Genshi trunk) 
    2222 
    2323You also need a database system and the corresponding python bindings. 
     
    2929 
    3030If you're using Python 2.4 and need pysqlite, you can download from  
    31 [http://code.google.com/p/pysqlite/downloads/list google code] the Windows 
    32 installers or the tar.gz archive for building from source:  
     31[http://code.google.com/p/pysqlite/downloads/list google code] the Windows installers or the tar.gz archive for building from source:  
    3332{{{ 
    3433$ tar xvfz <version>.tar.gz  
     
    3938This will extract the SQLite code and build the bindings.  
    4039 
    41 SQLite 2.x is no longer supported. For SQLite 3.x, the pysqlite 1.1.x 
    42 bindings are also no longer supported, use pysqlite 2.x. 
    43  
    44 See additional information in [trac:PySqlite PySqlite]. 
     40To install SQLite, your system may require the development headers. Without these you will get various GCC related errors when attempting to build: 
     41 
     42{{{ 
     43$ apt-get install libsqlite3-dev 
     44}}} 
     45 
     46SQLite 2.x is no longer supported, and neither is !PySqlite 1.1.x. 
     47 
     48A known bug !PySqlite versions 2.5.2-4 prohibits upgrade of trac databases 
     49from 0.11.x to 0.12. Please use versions 2.5.5 and newer or 2.5.1 and 
     50older. See [trac:#9434] for more detail. 
     51 
     52See additional information in [trac:PySqlite]. 
    4553 
    4654==== For the PostgreSQL database #ForPostgreSQL 
    4755 
    4856You need to install the database and its Python bindings: 
    49  * [http://www.postgresql.org/ PostgreSQL] 
     57 * [http://www.postgresql.org/ PostgreSQL], version 8.0 or later 
    5058 * [http://pypi.python.org/pypi/psycopg2 psycopg2] 
    5159 
     
    6068 * [http://sf.net/projects/mysql-python MySQLdb], version 1.2.2 or later 
    6169 
    62 It is '''very''' important to read carefully the  [trac:MySqlDb MySqlDb] page before creating the database. 
     70It is '''very''' important to read carefully the  [trac:MySqlDb] page before creating the database. 
    6371 
    6472=== Optional Dependencies 
     
    6775 
    6876===== Subversion ===== 
    69  * [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. 
    70  
    71 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 
    72  
    73  
    74 '''Please note:''' if using Subversion, Trac must be installed on the '''same machine'''. Remote repositories are currently [trac:ticket:493 not supported]. 
     77 
     78[http://subversion.apache.org/ Subversion] 1.5.x or 1.6.x and the '''''corresponding''''' Python bindings.  
     79 
     80There are [http://subversion.apache.org/packages.html pre-compiled SWIG bindings] available for various platforms. See also the [trac:TracSubversion] page for details about Windows packages. 
     81 
     82Older 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). 
     83 
     84Note that Trac '''doesn't''' use [http://pysvn.tigris.org/ PySVN], neither does it work yet with the newer `ctype`-style bindings.  
     85 
     86'''Please note:''' if using Subversion, Trac must be installed on the '''same machine'''. Remote repositories are currently [trac:#493 not supported]. 
    7587 
    7688 
    7789===== Others ===== 
    7890 
    79 Support for other version control systems is provided via third-parties. See [trac:PluginList PluginList] and [trac:VersioningSystemBackend VersioningSystemBackend]. 
     91Support for other version control systems is provided via third-parties. See [trac:PluginList] and [trac:VersionControlSystem]. 
    8092 
    8193==== Web Server ==== 
     
    8496Alternatively you configure Trac to run in any of the following environments. 
    8597 * [http://httpd.apache.org/ Apache] with  
    86    - [http://code.google.com/p/modwsgi/ mod_wsgi], see [wiki:TracModWSGI] and  
    87      http://code.google.com/p/modwsgi/wiki/IntegrationWithTrac 
    88    - [http://modpython.org/ mod_python 3.3.1], see TracModPython) 
    89  * a [http://www.fastcgi.com/ FastCGI]-capable web server (see TracFastCgi) 
    90  * an [http://tomcat.apache.org/connectors-doc/ajp/ajpv13a.html AJP]-capable web 
    91    server (see [trac:TracOnWindowsIisAjp TracOnWindowsIisAjp]) 
    92  * a CGI-capable web server (see TracCgi), '''but usage of Trac as a cgi script  
    93    is highly discouraged''', better use one of the previous options.  
     98   - [http://code.google.com/p/modwsgi/ mod_wsgi], see [wiki:TracModWSGI] (preferred) 
     99   - //[http://modpython.org/ mod_python 3.3.1], see TracModPython (deprecated)// 
     100 * any [http://www.fastcgi.com/ FastCGI]-capable web server, see TracFastCgi 
     101 * any [http://tomcat.apache.org/connectors-doc/ajp/ajpv13a.html AJP]-capable web 
     102   server, see [trac:TracOnWindowsIisAjp] 
     103 * IIS with [http://code.google.com/p/isapi-wsgi/ Isapi-wsgi], see [trac:TracOnWindowsIisIsapi] 
     104 * //as a last resort, a CGI-capable web server (see TracCgi), but usage of Trac as a cgi script  
     105   is highly discouraged, better use one of the previous options.// 
    94106    
    95107 
    96108==== Other Python Packages ==== 
    97109 
    98  * [http://babel.edgewall.org Babel], version >= 0.9.5,  
    99    needed for localization support 
     110 * [http://babel.edgewall.org Babel], version 0.9.5,  
     111   needed for localization support[[BR]] 
     112   ''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.  
    100113 * [http://docutils.sourceforge.net/ docutils], version >= 0.3.9  
    101114   for WikiRestructuredText. 
     
    109122   an internal time zone implementation. 
    110123 
    111 '''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]. 
     124'''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]. 
    112125 
    113126Please 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!). 
     
    116129== Installing Trac == 
    117130=== Using `easy_install` 
    118 One way to install Trac is using `setuptools`. 
     131One way to install Trac is using [http://pypi.python.org/pypi/setuptools setuptools]. 
    119132With setuptools you can install Trac from the subversion repository;  
    120133 
    121134A few examples: 
    122135 
    123  - install Trac 0.12: 
     136 - first install of the latest stable version Trac 0.12.3, with i18n support: 
    124137   {{{ 
     138   easy_install Babel==0.9.5 
    125139   easy_install Trac==0.12 
    126140   }}} 
    127  
    128  - install latest development version 0.12dev: 
     141   ''It's very important to run the two `easy_install` commands separately, otherwise the message catalogs won't be generated.'' 
     142 
     143 - upgrade to the latest stable version of Trac: 
    129144   {{{ 
    130    easy_install Trac==dev 
     145   easy_install -U Trac 
    131146   }}} 
    132    Note that in this case you won't have the possibility to run a localized version of Trac; 
    133    either use a released version or install from source  
    134  
    135 === Using `pip` 
     147 
     148 - upgrade to the latest trunk development version: 
     149   {{{ 
     150   easy_install -U Trac==dev 
     151   }}} 
     152 
     153For upgrades, reading the TracUpgrade page is mandatory, of course. 
     154 
     155{{{#!div style="border: 1pt dotted; margin: 1em" 
     156**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].  
     157}}} 
     158 
     159=== From source 
     160If 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]]. 
     161 
     162Be 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]. 
     163 
     164Once you've unpacked the Trac archive or performed the checkout, move in the top-level folder and do: 
     165{{{ 
     166$ python ./setup.py install 
     167}}} 
     168 
     169You'll need root permissions or equivalent for this step. 
     170 
     171This will byte-compile the python source code and install it as an .egg file or folder in the `site-packages` directory 
     172of your Python installation. The .egg will also contain all other resources needed by standard Trac, such as htdocs and templates. 
     173 
     174The 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. 
     175 
     176If 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): 
     177{{{ 
     178$ python ./setup.py install 
     179}}} 
     180Alternatively, 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`). 
     181 
     182=== Advanced Options === 
     183 
     184==== Custom location with `easy_install` 
     185 
     186To install Trac to a custom location, or find out about other advanced installation options, run: 
     187{{{ 
     188easy_install --help 
     189}}} 
     190 
     191Also see [http://docs.python.org/inst/inst.html Installing Python Modules] for detailed information. 
     192 
     193Specifically, you might be interested in: 
     194{{{ 
     195easy_install --prefix=/path/to/installdir 
     196}}} 
     197or, if installing Trac to a Mac OS X system: 
     198{{{ 
     199easy_install --prefix=/usr/local --install-dir=/Library/Python/2.5/site-packages 
     200}}} 
     201Note: 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 
     202 
     203The 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. 
     204 
     205==== Using `pip` 
    136206'pip' is an easy_install replacement that is very useful to quickly install python packages. 
    137207To get a trac installation up and running in less than 5 minutes: 
    138208 
    139 Assuming you want to have your entire pip installation in /opt/user/trac 
     209Assuming you want to have your entire pip installation in /opt/user/trac: 
    140210 
    141211 -  
     
    151221Make sure your OS specific headers are available for pip to automatically build PostgreSQL (libpq-dev) or MySQL (libmysqlclient-dev) bindings. 
    152222 
    153 pip 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  
    154  
    155 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) 
     223pip 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 . 
     224 
     225All 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) 
    156226 
    157227Additionally, you can install several trac plugins (listed [http://pypi.python.org/pypi?:action=search&term=trac&submit=search here]) through pip. 
    158228 
    159  
    160  
    161 === From source 
    162 Of course, using the python-typical setup at the top of the source directory also works. 
    163  
    164 You can obtain the source for a .tar.gz or .zip file corresponding to a release (e.g. Trac-0.12.tar.gz), or you can get the source directly from the repository (see Trac:SubversionRepository for details). 
    165  
    166 {{{ 
    167 $ python ./setup.py install 
    168 }}} 
    169  
    170 ''You'll need root permissions or equivalent for this step.'' 
    171  
    172 This will byte-compile the python source code and install it as an .egg file or folder in the `site-packages` directory 
    173 of your Python installation. The .egg will also contain all other resources needed by standard Trac, such as htdocs and templates. 
    174  
    175 The 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. 
    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 {{{ 
    179 $ python ./setup.py install 
    180 }}} 
    181 Alternatively, 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`). 
    182  
    183 === Advanced Options === 
    184  
    185 To install Trac to a custom location, or find out about other advanced installation options, run: 
    186 {{{ 
    187 easy_install --help 
    188 }}} 
    189  
    190 Also see [http://docs.python.org/inst/inst.html Installing Python Modules] for detailed information. 
    191  
    192 Specifically, you might be interested in: 
    193 {{{ 
    194 easy_install --prefix=/path/to/installdir 
    195 }}} 
    196 or, if installing Trac to a Mac OS X system: 
    197 {{{ 
    198 easy_install --prefix=/usr/local --install-dir=/Library/Python/2.5/site-packages 
    199 }}} 
    200 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.6/site-packages }}} by default 
    201  
    202 The 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. 
    203229 
    204230 
     
    226252}}} 
    227253 
    228 == Running the Standalone Server == 
     254{{{#!div class=important 
     255'''Warning:''' Please only use ASCII-characters for account name and project path, unicode characters are not supported there. 
     256}}} 
     257 
     258 
     259== Deploying Trac 
     260 
     261=== Running the Standalone Server === 
    229262 
    230263After having created a Trac environment, you can easily try the web interface by running the standalone server [wiki:TracStandalone tracd]: 
     
    238271}}} 
    239272 
    240 == Running Trac on a Web Server == 
    241  
    242 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. 
    243  
    244 Trac also supports [trac:TracOnWindowsIisAjp AJP] which may be your choice if you want to connect to IIS. 
    245  
    246 ==== Generating the Trac cgi-bin directory ==== 
     273{{{#!div style="border: 1pt dotted; margin: 1em" 
     274**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. 
     275 
     276To be effective system-wide a shell script with the `export` statement may be added to `/etc/profile.d`. To be effective for a user session the `export` statement may be added to `~/.profile`. 
     277{{{#!sh 
     278export PKG_RESOURCES_CACHE_ZIP_MANIFESTS=1 
     279}}} 
     280 
     281Alternatively, the variable can be set in the shell before executing `tracd`: 
     282{{{#!sh 
     283$ PKG_RESOURCES_CACHE_ZIP_MANIFESTS=1 tracd --port 8000 /path/to/myproject 
     284}}} 
     285}}} 
     286 
     287=== Running Trac on a Web Server === 
     288 
     289Trac provides various options for connecting to a "real" web server:  
     290 - [wiki:TracFastCgi FastCGI] 
     291 - [wiki:TracModWSGI mod_wsgi]  
     292 - //[wiki:TracModPython mod_python] (no longer recommended, as mod_python is not actively maintained anymore)// 
     293 - //[wiki:TracCgi CGI] (should not be used, as the performance is far from optimal)// 
     294 
     295Trac 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. 
     296 
     297==== Generating the Trac cgi-bin directory ==== #cgi-bin 
    247298 
    248299In 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]. 
     
    256307}}} 
    257308 
     309 
     310==== Mapping Static Resources ==== 
     311 
     312Out 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). 
     313 
     314Web 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. 
     315 
     316There 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. 
     317 
     318Note 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: 
     319[[TracAdminHelp(deploy)]] 
     320 
     321The target `<directory>` will then contain an `htdocs` directory with: 
     322 - `site/` - a copy of the environment's directory `htdocs/`  
     323 - `common/` - the static resources of Trac itself 
     324 - `<plugins>/` - one directory for each resource directory managed by the plugins enabled for this environment 
     325 
     326===== Example: Apache and `ScriptAlias` ===== #ScriptAlias-example 
     327 
     328Assuming the deployment has been done this way: 
     329{{{ 
     330$ trac-admin /var/trac/env deploy /path/to/trac/htdocs/common 
     331}}} 
     332 
     333Add 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: 
     334{{{ 
     335Alias /trac/chrome/common /path/to/trac/htdocs/common 
     336Alias /trac/chrome/site /path/to/trac/htdocs/site 
     337 
     338<Directory "/path/to/www/trac/htdocs"> 
     339  Order allow,deny 
     340  Allow from all 
     341</Directory> 
     342}}} 
     343 
     344If using mod_python, you might want to add this too (otherwise, the alias will be ignored): 
     345{{{ 
     346<Location "/trac/chrome/common/"> 
     347  SetHandler None 
     348</Location> 
     349}}} 
     350 
     351Note 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.  
     352 
     353Similarly, 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): 
     354{{{ 
     355Alias /trac/chrome/site /path/to/projectenv/htdocs 
     356 
     357<Directory "/path/to/projectenv/htdocs"> 
     358  Order allow,deny 
     359  Allow from all 
     360</Directory> 
     361}}} 
     362 
     363Alternatively 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: 
     364{{{ 
     365[trac] 
     366htdocs_location = http://static.example.org/trac-common/ 
     367}}} 
     368Note 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]). 
     369 
     370Of 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: 
     371{{{ 
     372$ ln -s /path/to/trac/htdocs/common /var/www/static.example.org/trac-common 
     373}}} 
     374 
     375 
    258376==== Setting up the Plugin Cache ==== 
    259377 
     
    262380== Configuring Authentication == 
    263381 
    264 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: 
    265  
    266  * TracStandalone if you use the standalone server, `tracd`. 
    267  * TracCgi if you use the CGI or FastCGI web front ends. 
    268  * [wiki:TracModWSGI] if you use the Apache mod_wsgi web front end. 
    269  * TracModPython if you use the Apache mod_python web front end. 
    270  
    271  
    272 == Automatic reference to the SVN changesets in Trac tickets == 
     382Trac 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. 
     383 
     384The process of adding, removing, and configuring user accounts for authentication depends on the specific way you run Trac.  
     385 
     386Please refer to one of the following sections: 
     387 * TracStandalone#UsingAuthentication if you use the standalone server, `tracd`. 
     388 * [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`. 
     389 * TracFastCgi if you're using another web server with FCGI support (Cherokee, Lighttpd, !LiteSpeed, nginx) 
     390 
     391== Granting admin rights to the admin user 
     392Grant admin rights to user admin: 
     393{{{ 
     394$ trac-admin /path/to/myproject permission add admin TRAC_ADMIN 
     395}}} 
     396This user will have an "Admin" entry menu that will allow you to admin your trac project. 
     397 
     398== Finishing the install 
     399 
     400=== Automatic reference to the SVN changesets in Trac tickets === 
    273401 
    274402You 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: 
     
    282410For more information, see the documentation of the `CommitTicketUpdater` component in the "Plugins" admin panel. 
    283411 
    284 == Using Trac == 
     412=== Using Trac === 
    285413 
    286414Once 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. 
    287415 
    288 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. 
     416Keep 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. 
    289417 
    290418'' Enjoy! '' 
     
    293421 
    294422---- 
    295 See also: [trac:TracInstallPlatforms TracInstallPlatforms], TracGuide, TracCgi, TracFastCgi, TracModPython, [wiki:TracModWSGI], TracUpgrade, TracPermissions 
     423See also: [trac:TracInstallPlatforms TracInstallPlatforms], TracGuide, TracUpgrade, TracPermissions