| 23 | | * [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) |
| 25 | | * [http://peak.telecommunity.com/DevCenter/setuptools setuptools], version >= 0.6 |
| 26 | | * [http://genshi.edgewall.org/wiki/Download Genshi], version >= 0.6 |
| | 18 | * [http://www.python.org/ Python], version >= 2.5 and < 3.0 |
| | 19 | (note that we dropped the support for Python 2.4 in this release) |
| | 20 | * [http://peak.telecommunity.com/DevCenter/setuptools setuptools], version >= 0.6, or better yet, [http://pypi.python.org/pypi/distribute distribute] |
| | 21 | * [http://genshi.edgewall.org/wiki/Download Genshi], version >= 0.6 (unreleased version 0.7dev should work as well) |
| 33 | | If you're using Python 2.5 or 2.6, you already have everything you need. |
| 34 | | |
| 35 | | If you're using Python 2.4 and need pysqlite, you can download from |
| 36 | | [http://code.google.com/p/pysqlite/downloads/list google code] |
| 37 | | installers or the tar.gz archive for building from source: |
| | 28 | As you must be using Python 2.5, 2.6 or 2.7, you already have the SQLite database bindings bundled with the standard distribution of Python (the `sqlite3` module). |
| | 29 | |
| | 30 | However, if you'd like, you can download the latest and greatest version of [[trac:Pysqlite]] from |
| | 31 | [http://code.google.com/p/pysqlite/downloads/list google code], where you'll find the Windows |
| | 32 | installers or the `tar.gz` archive for building from source: |
| 44 | | This will extract the SQLite code and build the bindings. |
| 45 | | |
| 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. |
| | 39 | This will download the latest SQLite code and build the bindings. |
| | 40 | |
| | 41 | SQLite 2.x is no longer supported. |
| | 42 | |
| | 43 | A known bug PySqlite versions 2.5.2-4 prohibits upgrade of trac databases |
| | 44 | from 0.11.x to 0.12. Please use versions 2.5.5 and newer or 2.5.1 and |
| | 45 | older. See #9434 for more detail. |
| | 140 | === Using `pip` |
| | 141 | 'pip' is an easy_install replacement that is very useful to quickly install python packages. |
| | 142 | To get a trac installation up and running in less than 5 minutes: |
| | 143 | |
| | 144 | Assuming you want to have your entire pip installation in `/opt/user/trac` |
| | 145 | |
| | 146 | - |
| | 147 | {{{ |
| | 148 | pip -E /opt/user/trac install trac psycopg2 |
| | 149 | }}} |
| | 150 | or |
| | 151 | - |
| | 152 | {{{ |
| | 153 | pip -E /opt/user/trac install trac mysql-python |
| | 154 | }}} |
| | 155 | |
| | 156 | Make sure your OS specific headers are available for pip to automatically build PostgreSQL (libpq-dev) or MySQL (libmysqlclient-dev) bindings. |
| | 157 | |
| | 158 | pip will automatically resolve all dependencies (like Genshi, pygments, etc.) and download the latest packages on pypi.python.org and create a self contained installation in `/opt/user/trac`. |
| | 159 | |
| | 160 | All commands (`tracd`, `trac-admin`) are available in `/opt/user/trac/bin`. This can also be leveraged for `mod_python` (using `PythonHandler` directive) and `mod_wsgi` (using `WSGIDaemonProcess` directive) |
| | 161 | |
| | 162 | Additionally, you can install several trac plugins (listed [http://pypi.python.org/pypi?:action=search&term=trac&submit=search here]) through pip. |
| | 163 | |
| | 164 | |
| | 165 | |
| 156 | | If you install from source and 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): |
| 157 | | {{{ |
| 158 | | $ python ./setup.py compile_catalog -f |
| 159 | | }}} |
| 160 | | (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) |
| 161 | | |
| | 182 | 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): |
| | 183 | {{{ |
| | 184 | $ python ./setup.py install |
| | 185 | }}} |
| | 186 | 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`). |
| 220 | | == Running Trac on a Web Server == |
| 221 | | |
| 222 | | 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. |
| 223 | | |
| 224 | | Trac also supports [trac:TracOnWindowsIisAjp AJP] which may be your choice if you want to connect to IIS. |
| 225 | | |
| 226 | | ==== Generating the Trac cgi-bin directory ==== |
| | 252 | === Running Trac on a Web Server === |
| | 253 | |
| | 254 | Trac provides various options for connecting to a "real" web server: |
| | 255 | - [wiki:TracFastCgi FastCGI] |
| | 256 | - [wiki:TracModWSGI mod_wsgi] |
| | 257 | - //[wiki:TracModPython mod_python] (no longer recommended, as mod_python is not actively maintained anymore)// |
| | 258 | - //[wiki:TracCgi CGI] (should not be used, as the performance is far from optimal)// |
| | 259 | |
| | 260 | 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. |
| | 261 | |
| | 262 | ==== Generating the Trac cgi-bin directory ==== #cgi-bin |
| | 274 | |
| | 275 | ==== Mapping Static Resources ==== |
| | 276 | |
| | 277 | 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). |
| | 278 | |
| | 279 | 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. |
| | 280 | |
| | 281 | 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. |
| | 282 | |
| | 283 | 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: |
| | 284 | [[TracAdminHelp(deploy)]] |
| | 285 | |
| | 286 | The target `<directory>` will then contain an `htdocs` directory with: |
| | 287 | - `site/` - a copy of the environment's directory `htdocs/` |
| | 288 | - `common/` - the static resources of Trac itself |
| | 289 | - `<plugins>/` - one directory for each resource directory managed by the plugins enabled for this environment |
| | 290 | |
| | 291 | ===== Example: Apache and `ScriptAlias` ===== #ScriptAlias-example |
| | 292 | |
| | 293 | Assuming the deployment has been done this way: |
| | 294 | {{{ |
| | 295 | $ trac-admin /var/trac/env deploy /path/to/trac/htdocs/common |
| | 296 | }}} |
| | 297 | |
| | 298 | 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: |
| | 299 | {{{ |
| | 300 | Alias /trac/chrome/common /path/to/trac/htdocs/common |
| | 301 | Alias /trac/chrome/site /path/to/trac/htdocs/site |
| | 302 | |
| | 303 | <Directory "/path/to/www/trac/htdocs"> |
| | 304 | Order allow,deny |
| | 305 | Allow from all |
| | 306 | </Directory> |
| | 307 | }}} |
| | 308 | |
| | 309 | If using mod_python, you might want to add this too (otherwise, the alias will be ignored): |
| | 310 | {{{ |
| | 311 | <Location "/trac/chrome/common/"> |
| | 312 | SetHandler None |
| | 313 | </Location> |
| | 314 | }}} |
| | 315 | |
| | 316 | 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. |
| | 317 | |
| | 318 | 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): |
| | 319 | {{{ |
| | 320 | Alias /trac/chrome/site /path/to/projectenv/htdocs |
| | 321 | |
| | 322 | <Directory "/path/to/projectenv/htdocs"> |
| | 323 | Order allow,deny |
| | 324 | Allow from all |
| | 325 | </Directory> |
| | 326 | }}} |
| | 327 | |
| | 328 | 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: |
| | 329 | {{{ |
| | 330 | [trac] |
| | 331 | htdocs_location = http://static.example.org/trac-common/ |
| | 332 | }}} |
| | 333 | 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]). |
| | 334 | |
| | 335 | 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: |
| | 336 | {{{ |
| | 337 | $ ln -s /path/to/trac/htdocs/common /var/www/static.example.org/trac-common |
| | 338 | }}} |
| | 339 | |
| | 340 | |
| 244 | | 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: |
| 245 | | |
| 246 | | * TracStandalone if you use the standalone server, `tracd`. |
| 247 | | * TracCgi if you use the CGI or FastCGI web front ends. |
| 248 | | * [wiki:TracModWSGI] if you use the Apache mod_wsgi web front end. |
| 249 | | * TracModPython if you use the Apache mod_python web front end. |
| 250 | | |
| 251 | | |
| 252 | | == Automatic reference to the SVN changesets in Trac tickets == |
| | 347 | 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. |
| | 348 | |
| | 349 | The process of adding, removing, and configuring user accounts for authentication depends on the specific way you run Trac. |
| | 350 | |
| | 351 | Please refer to one of the following sections: |
| | 352 | * TracStandalone#UsingAuthentication if you use the standalone server, `tracd`. |
| | 353 | * [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`. |
| | 354 | * TracFastCgi if you're using another web server with FCGI support (Cherokee, Lighttpd, !LiteSpeed, nginx) |
| | 355 | |
| | 356 | == Granting admin rights to the admin user |
| | 357 | Grant admin rights to user admin: |
| | 358 | {{{ |
| | 359 | $ trac-admin /path/to/myproject permission add admin TRAC_ADMIN |
| | 360 | }}} |
| | 361 | This user will have an "Admin" entry menu that will allow you to admin your trac project. |
| | 362 | |
| | 363 | == Finishing the install |
| | 364 | |
| | 365 | === Automatic reference to the SVN changesets in Trac tickets === |
