| 77 | | |
| 78 | | [http://subversion.apache.org/ Subversion] 1.5.x or 1.6.x and the '''''corresponding''''' Python bindings. |
| 79 | | |
| 80 | | There 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. |
| 81 | | |
| 82 | | 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). |
| 83 | | |
| 84 | | Note 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]. |
| | 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]. |
| 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.// |
| | 96 | - [http://code.google.com/p/modwsgi/ mod_wsgi], see [wiki:TracModWSGI] and |
| | 97 | http://code.google.com/p/modwsgi/wiki/IntegrationWithTrac |
| | 98 | - [http://modpython.org/ mod_python 3.3.1], deprecated: see TracModPython) |
| | 99 | * a [http://www.fastcgi.com/ FastCGI]-capable web server (see TracFastCgi) |
| | 100 | * an [http://tomcat.apache.org/connectors-doc/ajp/ajpv13a.html AJP]-capable web |
| | 101 | server (see [trac:TracOnWindowsIisAjp]) |
| | 102 | * a CGI-capable web server (see TracCgi), '''but usage of Trac as a cgi script |
| | 103 | is highly discouraged''', better use one of the previous options. |
| 269 | | === Running Trac on a Web Server === |
| 270 | | |
| 271 | | Trac provides various options for connecting to a "real" web server: |
| 272 | | - [wiki:TracFastCgi FastCGI] |
| 273 | | - [wiki:TracModWSGI mod_wsgi] |
| 274 | | - //[wiki:TracModPython mod_python] (no longer recommended, as mod_python is not actively maintained anymore)// |
| 275 | | - //[wiki:TracCgi CGI] (should not be used, as the performance is far from optimal)// |
| 276 | | |
| 277 | | 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. |
| 278 | | |
| 279 | | ==== Generating the Trac cgi-bin directory ==== #cgi-bin |
| | 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 ==== |
| 291 | | |
| 292 | | ==== Mapping Static Resources ==== |
| 293 | | |
| 294 | | 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''' and will cause abysmal performance). |
| 295 | | |
| 296 | | 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. |
| 297 | | |
| 298 | | There 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. |
| 299 | | |
| 300 | | Note 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: |
| 301 | | [[TracAdminHelp(deploy)]] |
| 302 | | |
| 303 | | The target `<directory>` will then contain an `htdocs` directory with: |
| 304 | | - `site/` - a copy of the environment's directory `htdocs/` |
| 305 | | - `common/` - the static resources of Trac itself |
| 306 | | - `<plugins>/` - one directory for each resource directory managed by the plugins enabled for this environment |
| 307 | | |
| 308 | | ===== Example: Apache and `ScriptAlias` ===== #ScriptAlias-example |
| 309 | | |
| 310 | | Assuming the deployment has been done this way: |
| 311 | | {{{ |
| 312 | | $ trac-admin /var/trac/env deploy /path/to/trac/htdocs/common |
| 313 | | }}} |
| 314 | | |
| 315 | | Add 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: |
| 316 | | {{{ |
| 317 | | Alias /trac/chrome/common /path/to/trac/htdocs/common |
| 318 | | Alias /trac/chrome/site /path/to/trac/htdocs/site |
| 319 | | |
| 320 | | <Directory "/path/to/www/trac/htdocs"> |
| 321 | | Order allow,deny |
| 322 | | Allow from all |
| 323 | | </Directory> |
| 324 | | }}} |
| 325 | | |
| 326 | | If using mod_python, you might want to add this too (otherwise, the alias will be ignored): |
| 327 | | {{{ |
| 328 | | <Location "/trac/chrome/common/"> |
| 329 | | SetHandler None |
| 330 | | </Location> |
| 331 | | }}} |
| 332 | | |
| 333 | | Note 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. |
| 334 | | |
| 335 | | Similarly, 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): |
| 336 | | {{{ |
| 337 | | Alias /trac/chrome/site /path/to/projectenv/htdocs |
| 338 | | |
| 339 | | <Directory "/path/to/projectenv/htdocs"> |
| 340 | | Order allow,deny |
| 341 | | Allow from all |
| 342 | | </Directory> |
| 343 | | }}} |
| 344 | | |
| 345 | | Alternatively 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: |
| 346 | | {{{ |
| 347 | | [trac] |
| 348 | | htdocs_location = http://static.example.org/trac-common/ |
| 349 | | }}} |
| 350 | | 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]). |
| 351 | | |
| 352 | | 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: |
| 353 | | {{{ |
| 354 | | $ ln -s /path/to/trac/htdocs/common /var/www/static.example.org/trac-common |
| 355 | | }}} |
| 356 | | |
| 357 | | |
| 364 | | 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. |
| 365 | | |
| 366 | | The process of adding, removing, and configuring user accounts for authentication depends on the specific way you run Trac. |
| 367 | | |
| 368 | | Please refer to one of the following sections: |
| 369 | | * TracStandalone#UsingAuthentication if you use the standalone server, `tracd`. |
| 370 | | * [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`. |
| 371 | | * TracFastCgi if you're using another web server with FCGI support (Cherokee, Lighttpd, !LiteSpeed, nginx) |
| 372 | | |
| 373 | | == Granting admin rights to the admin user |
| 374 | | Grant admin rights to user admin: |
| 375 | | {{{ |
| 376 | | $ trac-admin /path/to/myproject permission add admin TRAC_ADMIN |
| 377 | | }}} |
| 378 | | This user will have an "Admin" entry menu that will allow you to admin your trac project. |
| 379 | | |
| 380 | | == Finishing the install |
| 381 | | |
| 382 | | === Automatic reference to the SVN changesets in Trac tickets === |
| | 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 == |
