| 6 | | What follows are generic instructions for installing and setting up Trac and its requirements. While you can 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. |
| 7 | | |
| 8 | | == Short - Install a released version == |
| 9 | | For the quick install, make sure you have [http://python.org Python-2.5], [http://peak.telecommunity.com/DevCenter/EasyInstall#installing-easy-install easy_install] and SQlite-3.3.4 installed (or above). (You also might want to install python-dev to build genshi) |
| 10 | | {{{ |
| 11 | | sudo easy_install Trac |
| 12 | | }}} |
| 13 | | |
| 14 | | == Requirements == |
| 15 | | The hardware requirements for running Trac obviously depend on the expected data volume (number of wiki pages, tickets, revisions) and traffic. Very small projects will run fine with a 500MHz processor and 128MB RAM using SQLite. In general, the more RAM, the better. A fast hard disk also helps. |
| 16 | | |
| | 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 **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 | |
| | 8 | If 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 | |
| | 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 [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. |
| | 11 | |
| | 12 | [[PageOutline(2-3,Installation Steps,inline)]] |
| | 13 | |
| | 14 | == Dependencies == |
| | 15 | === Mandatory Dependencies |
| 24 | | * [http://genshi.edgewall.org/wiki/Download Genshi], version >= 0.5 (was version >= 0.4.1 on previous 0.11 release candidates) |
| 25 | | * You also need a database system and the corresponding python drivers for it. |
| 26 | | The database can be either SQLite, PostgreSQL or ''MySQL (experimental)''. |
| 27 | | * Optional if some plugins require it: [http://www.clearsilver.net/ ClearSilver] |
| 28 | | |
| 29 | | ==== For SQLite ==== |
| 30 | | |
| 31 | | * [http://www.sqlite.org/ SQLite], version 3.3.4 and above preferred (note: it is preinstalled in Python 2.5.2). |
| 32 | | * If not using Python-2.5: [http://pysqlite.org/ PySQLite], version 1.x (for SQLite 2.x) or version 2.x (for SQLite 3.x), version 2.3.2 preferred. For details see [trac:PySqlite PySqlite] |
| 33 | | |
| 34 | | ''Note: It appears that PySQLite 2.x is required for Trac 0.9+/SQLite 3.x if you plan to use the 'trac-post-commit-hook.py' script available from the 'contrib' section of the source repository.'' |
| 35 | | |
| 36 | | ''Note: Users of Mac OS X please take care; the Apple-supplied SQLite contains additional code to support file locking on network filesystems like AFP or SMB. This is not presently (3.3.6) in the mainline sources, so if you build your own SQLite from source it will not function correctly on such filesystems - typically it gives the error "{{{database is locked}}}". [http://www.alastairs-place.net/2006/07/sqlite_and_mac/ A patch] is available for version 3.3.6, based on Apple's code, otherwise you're probably best off using the Apple supplied version (presently 3.1.3).'' |
| 37 | | |
| 38 | | ==== For PostgreSQL ==== |
| 39 | | |
| 40 | | * [http://www.postgresql.org/ PostgreSQL] |
| 41 | | * [http://initd.org/projects/psycopg2 psycopg2] |
| 42 | | * See [trac:wiki:DatabaseBackend#Postgresql DatabaseBackend] |
| 43 | | |
| 44 | | '''Warning''': PostgreSQL 8.3 uses a strict type checking mechanism. To use Trac with the 8.3 Version of PostgreSQL, you will need [http://trac.edgewall.org/changeset/6512 trac-0.11] or later. |
| 45 | | |
| 46 | | ==== For MySQL ==== |
| 47 | | |
| 48 | | '''Warning''': MySQL support is currently ''still'' experimental. That means it works for some people, but several issues remain, in particular regarding the use of unicode and the key length in the repository cache. See [trac:MySqlDb MySqlDb] for more detailed information. |
| 49 | | |
| 50 | | * [http://mysql.com/ MySQL], version 4.1 or later |
| 51 | | * [http://sf.net/projects/mysql-python MySQLdb], version 1.2.1 or later |
| 52 | | |
| 53 | | == Optional Requirements == |
| | 21 | * [http://genshi.edgewall.org/wiki/Download Genshi], version >= 0.6 (but < 0.7dev, i.e. don't use Genshi trunk) |
| | 22 | |
| | 23 | You also need a database system and the corresponding python bindings. |
| | 24 | The database can be either SQLite, PostgreSQL or MySQL. |
| | 25 | |
| | 26 | ==== For the SQLite database #ForSQLite |
| | 27 | |
| | 28 | If you're using Python 2.5 or 2.6, you already have everything you need. |
| | 29 | |
| | 30 | If 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 installers or the tar.gz archive for building from source: |
| | 32 | {{{ |
| | 33 | $ tar xvfz <version>.tar.gz |
| | 34 | $ cd <version> |
| | 35 | $ python setup.py build_static install |
| | 36 | }}} |
| | 37 | |
| | 38 | This will extract the SQLite code and build the bindings. |
| | 39 | |
| | 40 | To 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 | |
| | 46 | SQLite 2.x is no longer supported, and neither is !PySqlite 1.1.x. |
| | 47 | |
| | 48 | A known bug !PySqlite versions 2.5.2-4 prohibits upgrade of trac databases |
| | 49 | from 0.11.x to 0.12. Please use versions 2.5.5 and newer or 2.5.1 and |
| | 50 | older. See [trac:#9434] for more detail. |
| | 51 | |
| | 52 | See additional information in [trac:PySqlite]. |
| | 53 | |
| | 54 | ==== For the PostgreSQL database #ForPostgreSQL |
| | 55 | |
| | 56 | You need to install the database and its Python bindings: |
| | 57 | * [http://www.postgresql.org/ PostgreSQL], version 8.0 or later |
| | 58 | * [http://pypi.python.org/pypi/psycopg2 psycopg2] |
| | 59 | |
| | 60 | See [trac:DatabaseBackend#Postgresql DatabaseBackend] for details. |
| | 61 | |
| | 62 | |
| | 63 | ==== For the MySQL database #ForMySQL |
| | 64 | |
| | 65 | Trac can now work quite well with MySQL, provided you follow the guidelines. |
| | 66 | |
| | 67 | * [http://mysql.com/ MySQL], version 5.0 or later |
| | 68 | * [http://sf.net/projects/mysql-python MySQLdb], version 1.2.2 or later |
| | 69 | |
| | 70 | It is '''very''' important to read carefully the [trac:MySqlDb] page before creating the database. |
| | 71 | |
| | 72 | === Optional Dependencies |
| 57 | | '''Please note:''' if using Subversion, Trac must be installed on the '''same machine'''. Remote repositories are currently not supported. |
| 58 | | |
| 59 | | * [http://subversion.tigris.org/ Subversion], version >= 1.0. (versions recommended: 1.2.4, 1.3.2 or 1.4.2) and the '''''corresponding''''' Python bindings. For troubleshooting, check [trac:TracSubversion TracSubversion] |
| 60 | | * Trac uses the [http://svnbook.red-bean.com/svnbook-1.1/ch08s02.html#svn-ch-8-sect-2.3 SWIG] bindings included in the Subversion distribution, '''not''' [http://pysvn.tigris.org/ PySVN] (which is sometimes confused with the standard SWIG bindings). |
| 61 | | * If Subversion was already installed without the SWIG bindings, on Unix you'll need to re-`configure` Subversion and `make swig-py`, `make install-swig-py`. |
| 62 | | * There are [http://subversion.tigris.org/servlets/ProjectDocumentList?folderID=91 pre-compiled bindings] available for win32. |
| 63 | | * Support for other version control systems is provided via third-parties. See [trac:PluginList PluginList] and [trac:VersioningSystemBackend VersioningSystemBackend]. |
| | 76 | ===== Subversion ===== |
| | 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]. |
| | 87 | |
| | 88 | |
| | 89 | ===== Others ===== |
| | 90 | |
| | 91 | Support for other version control systems is provided via third-parties. See [trac:PluginList] and [trac:VersionControlSystem]. |
| 66 | | * A CGI-capable web server (see TracCgi), or |
| 67 | | * a [http://www.fastcgi.com/ FastCGI]-capable web server (see TracFastCgi), or |
| 68 | | * an [http://tomcat.apache.org/connectors-doc/ajp/ajpv13a.html AJP]-capable web server (see [trac:TracOnWindowsIisAjp TracOnWindowsIisAjp]), or |
| 69 | | * [http://httpd.apache.org/ Apache] with [http://code.google.com/p/modwsgi/ mod_wsgi] (see [wiki:TracModWSGI] or http://code.google.com/p/modwsgi/wiki/IntegrationWithTrac) |
| 70 | | * This should work with Apache 1.3, 2.0 or 2.2 and promises to deliver more performance than using mod_python. A little less mature than mod_python. |
| 71 | | * [http://httpd.apache.org/ Apache] with [http://www.modpython.org/ mod_python 3.1.3+] (see TracModPython) |
| 72 | | * When installing mod_python the development versions of Python and Apache are required (actually the libraries and header files) |
| 73 | | |
| 74 | | For those stuck with Apache 1.3, it is also possible to get Trac working with [http://www.modpython.org/ mod_python 2.7] (see [wiki:TracModPython2.7 TracModPython2.7]). This guide hasn't been updated since 0.84, so it may or may not work. |
| 75 | | |
| 76 | | ==== Other Python Utilities ==== |
| 77 | | * [http://docutils.sourceforge.net/ docutils], version >= 0.3.9 for WikiRestructuredText. |
| 78 | | * [http://pygments.pocoo.org Pygments] for '''syntax highlighting''', although [http://silvercity.sourceforge.net/ SilverCity] >= 0.9.7 and/or [http://gnu.org/software/enscript/enscript.html GNU Enscript] are also possible. Refer to TracSyntaxColoring for details. |
| 79 | | * [http://pytz.sf.net pytz] to get a complete list of time zones, otherwise Trac will fall back on a shorter list from an internal time zone implementation. |
| 80 | | |
| 81 | | '''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]. |
| | 94 | A web server is optional because Trac is shipped with a server included, see the [#RunningtheStandaloneServer Running the Standalone Server ] section below. |
| | 95 | |
| | 96 | Alternatively you configure Trac to run in any of the following environments. |
| | 97 | * [http://httpd.apache.org/ Apache] with |
| | 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.// |
| | 106 | |
| | 107 | |
| | 108 | ==== Other Python Packages ==== |
| | 109 | |
| | 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. |
| | 113 | * [http://docutils.sourceforge.net/ docutils], version >= 0.3.9 |
| | 114 | for WikiRestructuredText. |
| | 115 | * [http://pygments.pocoo.org Pygments] for |
| | 116 | [wiki:TracSyntaxColoring syntax highlighting]. |
| | 117 | [http://silvercity.sourceforge.net/ SilverCity] and/or |
| | 118 | [http://gnu.org/software/enscript/enscript.html Enscript] may still be used |
| | 119 | but are deprecated and you really should be using Pygments. |
| | 120 | * [http://pytz.sf.net pytz] to get a complete list of time zones, |
| | 121 | otherwise Trac will fall back on a shorter list from |
| | 122 | an internal time zone implementation. |
| | 123 | |
| | 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]. |
| 86 | | |
| 87 | | One way to install Trac is using `setuptools`. |
| 88 | | With setuptools you can install Trac from the subversion repository; for example, |
| 89 | | to install release version 0.11 do: |
| 90 | | {{{ |
| 91 | | easy_install http://svn.edgewall.org/repos/trac/tags/trac-0.11 |
| 92 | | }}} |
| 93 | | |
| 94 | | But of course the python-typical setup at the top of the source directory also works: |
| | 130 | === Using `easy_install` |
| | 131 | One way to install Trac is using [http://pypi.python.org/pypi/setuptools setuptools]. |
| | 132 | With setuptools you can install Trac from the subversion repository; |
| | 133 | |
| | 134 | A few examples: |
| | 135 | |
| | 136 | - first install of the latest stable version Trac 0.12.3, with i18n support: |
| | 137 | {{{ |
| | 138 | easy_install Babel==0.9.5 |
| | 139 | easy_install Trac |
| | 140 | }}} |
| | 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: |
| | 144 | {{{ |
| | 145 | easy_install -U Trac |
| | 146 | }}} |
| | 147 | |
| | 148 | - upgrade to the latest trunk development version (0.13dev): |
| | 149 | {{{ |
| | 150 | easy_install -U Trac==dev |
| | 151 | }}} |
| | 152 | |
| | 153 | For upgrades, reading the TracUpgrade page is mandatory, of course. |
| | 154 | |
| | 155 | === From source |
| | 156 | 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]]. |
| | 157 | |
| | 158 | 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]. |
| | 159 | |
| | 160 | Once you've unpacked the Trac archive or performed the checkout, move in the top-level folder and do: |
| 135 | | [wiki:TracAdmin trac-admin] will prompt you for the information it needs to create the environment, such as the name of the project, the type and the path to an existing [wiki:TracEnvironment#SourceCodeRepository source code repository], the [wiki:TracEnvironment#DatabaseConnectionStrings database connection string], and so on. If you're not sure what to specify for one of these options, just leave it blank to use the default value. The database connection string in particular will always work as long as you have SQLite installed. Leaving the path to the source code repository empty will disable any functionality related to version control, but you can always add that back when the basic system is running. |
| 136 | | |
| 137 | | Also note that the values you specify here can be changed later by directly editing the [wiki:TracIni] configuration file. |
| 138 | | |
| 139 | | ''Note: The user account under which the web server runs will require write permissions to the environment directory and all the files inside. On Linux, with the web server running as user apache and group apache, enter:'' |
| 140 | | |
| 141 | | chown -R apache.apache /path/to/myproject |
| 142 | | |
| 143 | | '''Warning: If the trac.cgi files are not installed where you expect, then the current documentation is insufficient; it might be necessary to use the 'deploy' command in trac-admin. See tickets http://trac.edgewall.org/ticket/7312 and possibly http://trac.edgewall.org/ticket/6827''' |
| 144 | | |
| 145 | | == Running the Standalone Server == |
| | 236 | [TracAdmin trac-admin] will prompt you for the information it needs to create the environment, such as the name of the project and the [TracEnvironment#DatabaseConnectionStrings database connection string]. If you're not sure what to specify for one of these options, just press `<Enter>` to use the default value. |
| | 237 | |
| | 238 | Using the default database connection string in particular will always work as long as you have SQLite installed. |
| | 239 | For the other [DatabaseBackend database backends] you should plan ahead and already have a database ready to use at this point. |
| | 240 | |
| | 241 | Since 0.12, Trac doesn't ask for a [TracEnvironment#SourceCodeRepository source code repository] anymore when creating an environment. Repositories can be [TracRepositoryAdmin added] afterward, or the version control support can be disabled completely if you don't need it. |
| | 242 | |
| | 243 | Also note that the values you specify here can be changed later by directly editing the [TracIni conf/trac.ini] configuration file. |
| | 244 | |
| | 245 | Finally, make sure the user account under which the web front-end runs will have '''write permissions''' to the environment directory and all the files inside. This will be the case if you run `trac-admin ... initenv` as this user. If not, you should set the correct user afterwards. For example on Linux, with the web server running as user `apache` and group `apache`, enter: |
| | 246 | {{{ |
| | 247 | # chown -R apache.apache /path/to/myproject |
| | 248 | }}} |
| | 249 | |
| | 250 | {{{#!div class=important |
| | 251 | '''Warning:''' Please only use ASCII-characters for account name and project path, unicode characters are not supported there. |
| | 252 | }}} |
| | 253 | |
| | 254 | |
| | 255 | == Deploying Trac |
| | 256 | |
| | 257 | === Running the Standalone Server === |
| 157 | | |
| 158 | | == Running Trac on a Web Server == |
| 159 | | |
| 160 | | Trac provides three options for connecting to a "real" web server: [wiki:TracCgi CGI], [wiki:TracFastCgi FastCGI] and [wiki:TracModPython mod_python]. For decent performance, it is recommended that you use either FastCGI or mod_python. |
| 161 | | |
| 162 | | If you're not afraid of running newer code, you can also try running Trac on [wiki:TracModWSGI mod_wsgi]. This should deliver even better performance than mod_python, but the module isn't as extensively tested as mod_python. |
| 163 | | |
| 164 | | Trac also supports [trac:TracOnWindowsIisAjp AJP] which may be your choice if you want to connect to IIS. |
| | 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 |
| | 280 | |
| | 281 | 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]. |
| | 282 | |
| | 283 | 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: |
| | 284 | {{{ |
| | 285 | mkdir -p /usr/share/trac/projects/my-project |
| | 286 | trac-admin /usr/share/trac/projects/my-project initenv |
| | 287 | trac-admin /usr/share/trac/projects/my-project deploy /tmp/deploy |
| | 288 | mv /tmp/deploy/* /usr/share/trac |
| | 289 | }}} |
| | 290 | |
| | 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 | |
| 172 | | 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: |
| 173 | | |
| 174 | | * TracStandalone if you use the standalone server, `tracd`. |
| 175 | | * TracCgi if you use the CGI or FastCGI methods. |
| 176 | | * TracModPython if you use the mod_python method. |
| 177 | | |
| 178 | | == Automatic reference to the SVN changesets in Trac tickets == |
| 179 | | |
| 180 | | You can configure SVN to automatically add a reference to the changeset into the ticket comments, whenever files are committed to the repository. The description of the commit needs to contain one of the following formulas: |
| 181 | | * '''Refs #123''' - to reference this changeset in #123 ticket |
| 182 | | * '''Fixes #123''' - to reference this changeset and close #123 ticket with the default status ''fixed'' |
| 183 | | |
| 184 | | All you have to do is to edit the ''post-commit'' hook in your SVN repository and make it execute ''trac-post-commit-hook'' coming with Trac. |
| 185 | | |
| 186 | | If you are editing the ''post-commit'' hook for the first time you need to navigate to your SVN repository's hooks subfolder and rename existing there ''post-commit'' template: |
| 187 | | |
| 188 | | {{{ |
| 189 | | $ cd /path/to/svn/repository/hooks |
| 190 | | $ mv post-commit.tmpl post-commit |
| 191 | | }}} |
| 192 | | |
| 193 | | Next open it in any text editor and add a line with path to the Trac environment connected with this SVN repository and another line executing the ''trac-post-commit-hook'' script: |
| 194 | | |
| 195 | | {{{ |
| 196 | | REPOS="$1" |
| 197 | | REV="$2" |
| 198 | | TRAC_ENV="/var/lib/trac/mamut" |
| 199 | | |
| 200 | | /usr/bin/python /usr/local/bin/trac-post-commit-hook -p "$TRAC_ENV" -r "$REV" |
| 201 | | }}} |
| 202 | | |
| 203 | | Make sure that ''trac-post-commit-hook'' exists in above path with execution permissions for the same user which SVN is running from. This script can be found in contrib subfolder of your Trac distribution and the latest version can be always downloaded from [source:trunk/contrib/trac-post-commit-hook]. |
| 204 | | |
| 205 | | |
| 206 | | == Platform-specifics installations == |
| 207 | | |
| 208 | | * See [trac:TracInstallPlatforms TracInstallPlatforms] |
| 209 | | |
| 210 | | |
| 211 | | == Using Trac == |
| 212 | | |
| 213 | | Once you have your Trac site up and running, you should be able to browse your subversion repository, create tickets, view the timeline, etc. |
| 214 | | |
| 215 | | 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. |
| | 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 === |
| | 383 | |
| | 384 | 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: |
| | 385 | * '''`Refs #123`''' - to reference this changeset in `#123` ticket |
| | 386 | * '''`Fixes #123`''' - to reference this changeset and close `#123` ticket with the default status ''fixed'' |
| | 387 | |
| | 388 | 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. |
| | 389 | {{{ |
| | 390 | tracopt.ticket.commit_updater.* = enabled |
| | 391 | }}} |
| | 392 | For more information, see the documentation of the `CommitTicketUpdater` component in the "Plugins" admin panel. |
| | 393 | |
| | 394 | === Using Trac === |
| | 395 | |
| | 396 | Once 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. |
| | 397 | |
| | 398 | Keep 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. |
