| 74 | | ==== Version Control System ==== |
| 75 | | |
| 76 | | ===== Subversion ===== |
| 77 | | * [http://subversion.apache.org/ Subversion], 1.5.x or 1.6.x and the '''''corresponding''''' Python bindings. Older 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). |
| 78 | | |
| 79 | | 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. TracSubversion points you to [http://alagazam.net Algazam], which works for me under Python 2.6.) |
| 80 | | |
| 81 | | Note that Trac '''doesn't''' use [http://pysvn.tigris.org/ PySVN], neither does it work yet with the newer `ctype`-style bindings. [Is there a ticket for implementing ctype bindings?] |
| 82 | | |
| 83 | | |
| 84 | | '''Please note:''' if using Subversion, Trac must be installed on the '''same machine'''. Remote repositories are currently [trac:ticket:493 not supported]. |
| 85 | | |
| 86 | | |
| 87 | | ===== Others ===== |
| 88 | | |
| 89 | | Support for other version control systems is provided via third-parties. See [trac:PluginList] and [trac:VersioningSystemBackend]. |
| 90 | | |
| 91 | | ==== Web Server ==== |
| 92 | | A web server is optional because Trac is shipped with a server included, see the [#RunningtheStandaloneServer Running the Standalone Server ] section below. |
| 93 | | |
| 94 | | Alternatively you configure Trac to run in any of the following environments. |
| | 50 | ==== Subversion |
| | 51 | |
| | 52 | [http://subversion.apache.org/ Subversion], 1.6.x or later and the '''''corresponding''''' Python bindings. |
| | 53 | |
| | 54 | 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.) |
| | 55 | |
| | 56 | For troubleshooting information, see the [trac:TracSubversion#Troubleshooting TracSubversion] page. |
| | 57 | |
| | 58 | {{{#!div style="border: 1pt dotted; margin: 1em" |
| | 59 | **Note:** |
| | 60 | * Trac '''doesn't''' use [http://pysvn.tigris.org/ PySVN], nor does it work yet with the newer `ctype`-style bindings. |
| | 61 | * If using Subversion, Trac must be installed on the '''same machine'''. Remote repositories are currently [trac:ticket:493 not supported]. |
| | 62 | }}} |
| | 63 | |
| | 64 | ==== Git |
| | 65 | |
| | 66 | [http://git-scm.com/ Git] 1.5.6 or later is supported. More information is available on the [trac:TracGit] page. |
| | 67 | |
| | 68 | ==== Other Version Control Systems |
| | 69 | |
| | 70 | Support for other version control systems is provided via third-party plugins. See [trac:PluginList#VersionControlSystems] and [trac:VersionControlSystem]. |
| | 71 | |
| | 72 | ==== Web Server |
| | 73 | A web server is optional because Trac is shipped with a server included, see the [#RunningtheStandaloneServer Running the Standalone Server] section below. |
| | 74 | |
| | 75 | Alternatively you can configure Trac to run in any of the following environments: |
| 134 | | - first install of the latest stable version Trac 0.12.1, with i18n support: |
| 135 | | {{{ |
| 136 | | easy_install Babel==0.9.5 Genshi==0.6 |
| 137 | | easy_install Trac |
| 138 | | }}} |
| 139 | | ''It's very important to run the two `easy_install` commands separately, otherwise the message catalogs won't be generated.'' |
| 140 | | |
| 141 | | - upgrade to the latest stable version of Trac: |
| 142 | | {{{ |
| 143 | | easy_install -U Trac |
| 144 | | }}} |
| 145 | | |
| 146 | | - upgrade to the latest trunk development version (0.13dev): |
| 147 | | {{{ |
| 148 | | easy_install -U Trac==dev |
| 149 | | }}} |
| 150 | | |
| 151 | | For upgrades, reading the TracUpgrade page is mandatory, of course. |
| 152 | | |
| 153 | | === From source |
| 154 | | If 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]]. |
| 155 | | |
| 156 | | Be 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]. |
| 157 | | |
| 158 | | Once you've unpacked the Trac archive or performed the checkout, move in the top-level folder and do: |
| 159 | | {{{ |
| 160 | | $ python ./setup.py install |
| 161 | | }}} |
| 162 | | |
| 163 | | ''You'll need root permissions or equivalent for this step.'' |
| 164 | | |
| 165 | | This will byte-compile the python source code and install it as an .egg file or folder in the `site-packages` directory |
| 166 | | of your Python installation. The .egg will also contain all other resources needed by standard Trac, such as htdocs and templates. |
| 167 | | |
| 168 | | 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. |
| 169 | | |
| 170 | | 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): |
| 171 | | {{{ |
| 172 | | $ python ./setup.py install |
| 173 | | }}} |
| 174 | | 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`). |
| 175 | | |
| 176 | | === Advanced Options === |
| 177 | | |
| 178 | | To install Trac to a custom location, or find out about other advanced installation options, run: |
| 179 | | {{{ |
| 180 | | easy_install --help |
| 181 | | }}} |
| 182 | | |
| 183 | | Also see [http://docs.python.org/inst/inst.html Installing Python Modules] for detailed information. |
| 184 | | |
| 185 | | Specifically, you might be interested in: |
| 186 | | {{{ |
| 187 | | easy_install --prefix=/path/to/installdir |
| 188 | | }}} |
| 189 | | or, if installing Trac to a Mac OS X system: |
| 190 | | {{{ |
| 191 | | easy_install --prefix=/usr/local --install-dir=/Library/Python/2.5/site-packages |
| 192 | | }}} |
| 193 | | 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 |
| 194 | | |
| 195 | | 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. |
| | 116 | - Install the latest stable version of Trac: |
| | 117 | {{{#!sh |
| | 118 | $ easy_install Trac |
| | 119 | }}} |
| | 120 | - Install latest development version: |
| | 121 | {{{#!sh |
| | 122 | $ easy_install http://download.edgewall.org/trac/Trac-latest-dev.tar.gz |
| | 123 | }}} |
| | 124 | Note that in this case you won't have the possibility to run a localized version of Trac; |
| | 125 | either use a released version or install from source |
| | 126 | |
| | 127 | More information can be found on the [trac:wiki:setuptools setuptools] page. |
| | 128 | |
| | 129 | {{{#!div style="border: 1pt dotted; margin: 1em" |
| | 130 | **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 [#DeployingTrac Deploying Trac]. |
| | 131 | }}} |
| 208 | | - |
| 209 | | {{{ |
| 210 | | pip -E /opt/user/trac install trac mysql-python |
| 211 | | }}} |
| 212 | | |
| 213 | | Make sure your OS specific headers are available for pip to automatically build PostgreSQL (libpq-dev) or MySQL (libmysqlclient-dev) bindings. |
| 214 | | |
| 215 | | 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 . |
| 216 | | |
| 217 | | 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) |
| 218 | | |
| 219 | | Additionally, you can install several trac plugins (listed [http://pypi.python.org/pypi?:action=search&term=trac&submit=search here]) through pip. |
| 220 | | |
| 221 | | |
| 222 | | |
| 223 | | == Creating a Project Environment == |
| 224 | | |
| 225 | | A [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. |
| 226 | | |
| 227 | | A new environment is created using [wiki:TracAdmin trac-admin]: |
| 228 | | {{{ |
| | 143 | {{{#!sh |
| | 144 | $ pip install trac mysql-python |
| | 145 | }}} |
| | 146 | |
| | 147 | Make sure your OS specific headers are available for pip to automatically build PostgreSQL (`libpq-dev`) or MySQL (`libmysqlclient-dev`) bindings. |
| | 148 | |
| | 149 | 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`. |
| | 150 | |
| | 151 | 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) |
| | 152 | |
| | 153 | Additionally, you can install several Trac plugins (listed [https://pypi.python.org/pypi?:action=browse&show=all&c=516 here]) through pip. |
| | 154 | |
| | 155 | === From source |
| | 156 | 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. |
| | 157 | |
| | 158 | {{{#!sh |
| | 159 | $ python ./setup.py install |
| | 160 | }}} |
| | 161 | |
| | 162 | ''You will need root permissions or equivalent for this step.'' |
| | 163 | |
| | 164 | This will byte-compile the Python source code and install it as an .egg file or folder in the `site-packages` directory |
| | 165 | of your Python installation. The .egg will also contain all other resources needed by standard Trac, such as `htdocs` and `templates`. |
| | 166 | |
| | 167 | 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): |
| | 168 | {{{#!sh |
| | 169 | $ python ./setup.py install |
| | 170 | }}} |
| | 171 | 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`). |
| | 172 | |
| | 173 | === Using installer |
| | 174 | |
| | 175 | On Windows, Trac can be installed using the exe installers available on the [trac:TracDownload] page. Installers are available for the 32-bit and 64-bit versions of Python. Make sure to use the installer that matches the architecture of your Python installation. |
| | 176 | |
| | 177 | === Using package manager |
| | 178 | |
| | 179 | Trac may be available in your platform's package repository. Note however, that the version provided by your package manager may not be the latest release. |
| | 180 | |
| | 181 | === Advanced `easy_install` Options |
| | 182 | |
| | 183 | To install Trac to a custom location, or find out about other advanced installation options, run: |
| | 184 | {{{#!sh |
| | 185 | $ easy_install --help |
| | 186 | }}} |
| | 187 | |
| | 188 | Also see [http://docs.python.org/2/install/index.html Installing Python Modules] for detailed information. |
| | 189 | |
| | 190 | Specifically, you might be interested in: |
| | 191 | {{{#!sh |
| | 192 | $ easy_install --prefix=/path/to/installdir |
| | 193 | }}} |
| | 194 | or, if installing Trac on a Mac OS X system: |
| | 195 | {{{#!sh |
| | 196 | $ easy_install --prefix=/usr/local --install-dir=/Library/Python/2.6/site-packages |
| | 197 | }}} |
| | 198 | |
| | 199 | {{{#!div style="border: 1pt dotted; margin: 1em" |
| | 200 | **Mac OS X Note:** On Mac OS X 10.6, running `easy_install trac` will install into `/usr/local` and `/Library/Python/2.6/site-packages` by default. |
| | 201 | |
| | 202 | The `tracd` and `trac-admin` commands will be placed in `/usr/local/bin` and will install the Trac libraries and dependencies into `/Library/Python/2.6/site-packages`, which is Apple's preferred location for third-party Python application installations. |
| | 203 | }}} |
| | 204 | |
| | 205 | == Creating a Project Environment |
| | 206 | |
| | 207 | A [TracEnvironment Trac environment] is the backend where Trac stores information like wiki pages, tickets, reports, settings, etc. An environment is a directory that contains a human-readable [TracIni configuration file], and other files and directories. |
| | 208 | |
| | 209 | A new environment is created using [TracAdmin trac-admin]: |
| | 210 | {{{#!sh |
| 263 | | == Running Trac on a Web Server == |
| 264 | | |
| 265 | | 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. |
| 266 | | |
| 267 | | Trac also supports [trac:TracOnWindowsIisAjp AJP] which may be your choice if you want to connect to IIS. |
| 268 | | |
| 269 | | ==== Generating the Trac cgi-bin directory ==== |
| 270 | | |
| 271 | | 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 [wiki:TracAdmin trac-admin]. |
| 272 | | |
| 273 | | There 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: |
| 274 | | {{{ |
| 275 | | mkdir -p /usr/share/trac/projects/my-project |
| 276 | | trac-admin /usr/share/trac/projects/my-project initenv |
| 277 | | trac-admin /usr/share/trac/projects/my-project deploy /tmp/deploy |
| 278 | | mv /tmp/deploy/* /usr/share/trac |
| 279 | | }}} |
| 280 | | |
| 281 | | ==== Setting up the Plugin Cache ==== |
| 282 | | |
| 283 | | 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. |
| 284 | | |
| 285 | | == Configuring Authentication == |
| 286 | | |
| 287 | | 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: |
| 288 | | |
| 289 | | * TracStandalone if you use the standalone server, `tracd`. |
| 290 | | * TracCgi if you use the CGI or FastCGI web front ends. |
| 291 | | * [wiki:TracModWSGI] if you use the Apache mod_wsgi web front end. |
| 292 | | * TracModPython if you use the Apache mod_python web front end. |
| 293 | | |
| 294 | | |
| 295 | | == Automatic reference to the SVN changesets in Trac tickets == |
| 296 | | |
| 297 | | You 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: |
| 298 | | * '''`Refs #123`''' - to reference this changeset in `#123` ticket |
| 299 | | * '''`Fixes #123`''' - to reference this changeset and close `#123` ticket with the default status ''fixed'' |
| 300 | | |
| 301 | | This 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. |
| 302 | | {{{ |
| 303 | | tracopt.ticket.commit_updater.* = enabled |
| 304 | | }}} |
| 305 | | For more information, see the documentation of the `CommitTicketUpdater` component in the "Plugins" admin panel. |
| 306 | | |
| 307 | | == Using Trac == |
| | 267 | === Running Trac on a Web Server |
| | 268 | |
| | 269 | Trac provides various options for connecting to a "real" web server: |
| | 270 | - [TracFastCgi FastCGI] |
| | 271 | - [wiki:TracModWSGI Apache with mod_wsgi] |
| | 272 | - [TracModPython Apache with mod_python] |
| | 273 | - [TracCgi CGI] //(should not be used, as the performance is far from optimal)// |
| | 274 | |
| | 275 | Trac 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. |
| | 276 | |
| | 277 | ==== Generating the Trac cgi-bin directory #cgi-bin |
| | 278 | |
| | 279 | Application scripts for CGI, FastCGI and mod-wsgi can be generated using the [TracAdmin trac-admin] `deploy` command: |
| | 280 | [[TracAdminHelp(deploy)]] |
| | 281 | |
| | 282 | Grant the web server execution right on scripts in the `cgi-bin` directory. |
| | 283 | |
| | 284 | For example, the following yields a typical directory structure: |
| | 285 | {{{#!sh |
| | 286 | $ mkdir -p /var/trac |
| | 287 | $ trac-admin /var/trac/<project> initenv |
| | 288 | $ trac-admin /var/trac/<project> deploy /var/www |
| | 289 | $ ls /var/www |
| | 290 | cgi-bin htdocs |
| | 291 | $ chmod ugo+x /var/www/cgi-bin/* |
| | 292 | }}} |
| | 293 | |
| | 294 | ==== Mapping Static Resources |
| | 295 | |
| | 296 | Without additional configuration, Trac will handle requests for static resources such as stylesheets and images. For anything other than a TracStandalone deployment, this is not optimal as the web server can be set up to directly serve the static resources. For CGI setup, this is '''highly undesirable''' as it causes abysmal performance. |
| | 297 | |
| | 298 | 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 their location on the file system. We can map requests for static resources directly to directories on the file system, to avoid Trac processing the requests. |
| | 299 | |
| | 300 | There are two primary URL paths for static resources: `/chrome/common` and `/chrome/site`. Plugins can add their own resources, usually accessible at the `/chrome/<plugin>` path. |
| | 301 | |
| | 302 | A single `/chrome` alias can used if the static resources are extracted for all plugins. This means that the `deploy` command (discussed in the previous section) must be executed after installing or updating a plugin that provides static resources, or after modifying resources in the `$env/htdocs` directory. This is probably appropriate for most installations but may not be what you want if, for example, you wish to upload plugins through the //Plugins// administration page. |
| | 303 | |
| | 304 | The `deploy` command creates an `htdocs` directory with: |
| | 305 | - `common/` - the static resources of Trac |
| | 306 | - `site/` - a copy of the environment's `htdocs/` directory |
| | 307 | - `shared` - the static resources shared by multiple Trac environments, with a location defined by the `[inherit]` `htdocs_dir` option |
| | 308 | - `<plugin>/` - one directory for each resource directory provided by the plugins enabled for this environment |
| | 309 | |
| | 310 | The example that follows will create a single `/chrome` alias. If that isn't the correct approach for your installation you simply need to create more specific aliases: |
| | 311 | {{{#!apache |
| | 312 | Alias /trac/chrome/common /path/to/trac/htdocs/common |
| | 313 | Alias /trac/chrome/site /path/to/trac/htdocs/site |
| | 314 | Alias /trac/chrome/shared /path/to/trac/htdocs/shared |
| | 315 | Alias /trac/chrome/<plugin> /path/to/trac/htdocs/<plugin> |
| | 316 | }}} |
| | 317 | |
| | 318 | ===== Example: Apache and `ScriptAlias` #ScriptAlias-example |
| | 319 | |
| | 320 | Assuming the deployment has been done this way: |
| | 321 | {{{#!sh |
| | 322 | $ trac-admin /var/trac/<project> deploy /var/www |
| | 323 | }}} |
| | 324 | |
| | 325 | Add the following snippet to Apache configuration, changing paths to match your deployment. The snippet must be placed ''before'' the `ScriptAlias` or `WSGIScriptAlias` directive, because those directives map all requests to the Trac application: |
| | 326 | {{{#!apache |
| | 327 | Alias /trac/chrome /path/to/trac/htdocs |
| | 328 | |
| | 329 | <Directory "/path/to/www/trac/htdocs"> |
| | 330 | # For Apache 2.2 |
| | 331 | <IfModule !mod_authz_core.c> |
| | 332 | Order allow,deny |
| | 333 | Allow from all |
| | 334 | </IfModule> |
| | 335 | # For Apache 2.4 |
| | 336 | <IfModule mod_authz_core.c> |
| | 337 | Require all granted |
| | 338 | </IfModule> |
| | 339 | </Directory> |
| | 340 | }}} |
| | 341 | |
| | 342 | If using mod_python, add this too, otherwise the alias will be ignored: |
| | 343 | {{{#!apache |
| | 344 | <Location "/trac/chrome/common"> |
| | 345 | SetHandler None |
| | 346 | </Location> |
| | 347 | }}} |
| | 348 | |
| | 349 | Alternatively, if you wish to serve static resources directly from your project's `htdocs` directory rather than the location to which the files are extracted with the `deploy` command, 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: |
| | 350 | {{{#!apache |
| | 351 | Alias /trac/chrome/site /path/to/projectenv/htdocs |
| | 352 | |
| | 353 | <Directory "/path/to/projectenv/htdocs"> |
| | 354 | # For Apache 2.2 |
| | 355 | <IfModule !mod_authz_core.c> |
| | 356 | Order allow,deny |
| | 357 | Allow from all |
| | 358 | </IfModule> |
| | 359 | # For Apache 2.4 |
| | 360 | <IfModule mod_authz_core.c> |
| | 361 | Require all granted |
| | 362 | </IfModule> |
| | 363 | </Directory> |
| | 364 | }}} |
| | 365 | |
| | 366 | Another alternative to aliasing `/trac/chrome/common` is having Trac generate direct links for those static resources (and only those), using the [TracIni#trac-section htdocs_location] configuration setting: |
| | 367 | {{{#!ini |
| | 368 | [trac] |
| | 369 | htdocs_location = http://static.example.org/trac-common/ |
| | 370 | }}} |
| | 371 | |
| | 372 | Note that this makes it easy to have a dedicated domain serve those static resources, preferentially cookie-less. |
| | 373 | |
| | 374 | Of 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: |
| | 375 | {{{#!sh |
| | 376 | $ ln -s /path/to/trac/htdocs/common /var/www/static.example.org/trac-common |
| | 377 | }}} |
| | 378 | |
| | 379 | ==== Setting up the Plugin Cache #egg-cache |
| | 380 | |
| | 381 | 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. |
| | 382 | |
| | 383 | If you setup hook scripts that call Trac, such as the Subversion post-commit hook script provided in the `/contrib` directory, make sure you define the `PYTHON_EGG_CACHE` environment variable within these scripts as well. |
| | 384 | |
| | 385 | == Configuring Authentication |
| | 386 | |
| | 387 | 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. |
| | 388 | |
| | 389 | The process of adding, removing, and configuring user accounts for authentication depends on the specific way you run Trac. |
| | 390 | |
| | 391 | Please refer to one of the following sections: |
| | 392 | * TracStandalone#UsingAuthentication if you use the standalone server, `tracd`. |
| | 393 | * [wiki:TracModWSGI#ConfiguringAuthentication TracModWSGI#ConfiguringAuthentication] if you use the Apache web server, with any of its front end: `mod_wsgi`, `mod_python`, `mod_fcgi` or `mod_fastcgi`. |
| | 394 | * TracFastCgi if you're using another web server with FCGI support (Cherokee, Lighttpd, !LiteSpeed, nginx) |
| | 395 | |
| | 396 | [trac:TracAuthenticationIntroduction] also contains some useful information for beginners. |
| | 397 | |
| | 398 | == Granting admin rights to the admin user |
| | 399 | Grant admin rights to user admin: |
| | 400 | {{{#!sh |
| | 401 | $ trac-admin /path/to/myproject permission add admin TRAC_ADMIN |
| | 402 | }}} |
| | 403 | |
| | 404 | This user will have an //Admin// navigation item that directs to pages for administering your Trac project. |
| | 405 | |
| | 406 | == Configuring Trac |
| | 407 | |
| | 408 | TracRepositoryAdmin provides information on configuring version control repositories for your project. |
| | 409 | |
| | 410 | == Using Trac |
