| 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). |
| 10 | | {{{ |
| 11 | | sudo easy_install Trac==0.11 |
| 12 | | }}} |
| 13 | | |
| 14 | | == Requirements - also older versions possible == |
| | 9 | See TracUpgrade for instructions on how to upgrade an existing installation. |
| | 10 | |
| | 11 | |
| | 12 | == Quick Install a Released Version == |
| | 13 | For a quick install, first make sure you have [http://python.org/download Python] (2.3-2.6) and [http://peak.telecommunity.com/DevCenter/EasyInstall#installing-easy-install easy_install]. |
| | 14 | |
| | 15 | Then enter (''omitting 'sudo' if not applicable'') |
| | 16 | {{{ |
| | 17 | sudo easy_install Trac |
| | 18 | }}} |
| | 19 | to install Trac, SQLite, and Genshi. |
| | 20 | |
| | 21 | |
| | 22 | == Requirements == |
| | 23 | 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. |
| 21 | | * See instructions in ["TracOnWindows/Python2.5"] |
| 22 | | * [http://peak.telecommunity.com/DevCenter/setuptools setuptools], version >= 0.6 |
| 23 | | * [http://genshi.edgewall.org/wiki/Download Genshi], version >= 0.4.1 |
| | 30 | * See instructions in [trac:wiki:TracOnWindows/Python2.5 TracOnWindows/Python2.5] |
| | 31 | * [wiki:setuptools], version >= 0.6 |
| | 32 | * [http://genshi.edgewall.org/wiki/Download Genshi], version >= 0.5 (was version >= 0.4.1 on previous 0.11 release candidates) |
| 25 | | The database can be either SQLite, PostgreSQL or ''MySQL (experimental)''. |
| 26 | | * optional if some plugins require it: [http://www.clearsilver.net/ ClearSilver] |
| 27 | | |
| 28 | | === For SQLite === |
| 29 | | |
| 30 | | * [http://www.sqlite.org/ SQLite], version 3.3.4 and above preferred. |
| 31 | | * 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 PySqlite |
| 32 | | |
| 33 | | ''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.'' |
| 34 | | |
| 35 | | ''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).'' |
| 36 | | |
| 37 | | === For PostgreSQL === |
| | 34 | The database can be either SQLite, PostgreSQL or MySQL. |
| | 35 | * Optional if some plugins require it: [http://www.clearsilver.net/ ClearSilver] |
| | 36 | |
| | 37 | ==== For SQLite ==== |
| | 38 | |
| | 39 | If you're using Python 2.5 or 2.6, you already have everything you need. |
| | 40 | |
| | 41 | If you're using Python 2.3 or 2.4 and need pysqlite, you can download from |
| | 42 | [http://code.google.com/p/pysqlite/downloads/list google code] the Windows |
| | 43 | installers or the tar.gz archive for building from source: |
| | 44 | {{{ |
| | 45 | $ tar xvfz <version>.tar.gz |
| | 46 | $ cd <version> |
| | 47 | $ python setup.py build_static install |
| | 48 | }}} |
| | 49 | |
| | 50 | That way, the latest SQLite version will be downloaded and built into the |
| | 51 | bindings. |
| | 52 | |
| | 53 | If you're still using SQLite 2.x, you'll need pysqlite 1.0.x, although this |
| | 54 | package is not easy to find anymore. For SQLite 3.x, try not to use |
| | 55 | pysqlite 1.1.x, which has been deprecated in favor of pysqlite 2.x. |
| | 56 | |
| | 57 | See additional information in [trac:PySqlite PySqlite]. |
| | 58 | |
| | 59 | ==== For PostgreSQL ==== |
| 55 | | '''Please note:''' if using Subversion, Trac must be installed on the '''same machine'''. Remote repositories are currently not supported |
| 56 | | |
| 57 | | * [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 TracSubversion |
| | 79 | '''Please note:''' if using Subversion, Trac must be installed on the '''same machine'''. Remote repositories are currently not supported (although Windows UNC paths such as {{{\\machine_name\path\to\svn}}} do work). |
| | 80 | |
| | 81 | * [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] |
| 79 | | '''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 MailingList or IrcChannel. |
| 80 | | |
| 81 | | Please refer to the documentation of these packages to find out how they are best installed. In addition, most of the [wiki: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!). |
| | 103 | '''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]. |
| | 104 | |
| | 105 | Please 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!). |
| 159 | | If you're not afraid of running development code, you can also try running Trac on [wiki:TracModWSGI mod_wsgi]. This should deliver even better performance than mod_python, but the module is not considered stable just yet. |
| | 181 | 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. |
| | 182 | |
| | 183 | Trac also supports [trac:TracOnWindowsIisAjp AJP] which may be your choice if you want to connect to IIS. |
| | 184 | |
| | 185 | ==== Generating the Trac cgi-bin directory ==== |
| | 186 | |
| | 187 | In order for Trac to function properly with FastCGI or mod_python, you need to have a trac.cgi file. This is an executable which loads the appropriate Python code. It can be generated using the `deploy` option of [wiki:TracAdmin trac-admin]. |
| | 188 | |
| | 189 | 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: |
| | 190 | {{{ |
| | 191 | mkdir -p /usr/share/trac/projects/my-project |
| | 192 | trac-admin /usr/share/trac/projects/my-project initenv |
| | 193 | trac-admin /usr/share/trac/projects/my-project deploy /tmp/deploy |
| | 194 | mv /tmp/deploy/* /usr/share/trac |
| | 195 | }}} |
| | 196 | |
| | 197 | ==== Setting up the Plugin Cache ==== |
| | 198 | |
| | 199 | 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. |
| 169 | | == Trac 0.11 & SVN on Mac OS X Leopard (10.5) == |
| 170 | | |
| 171 | | * TracOnLeopardServer |
| | 209 | == Automatic reference to the SVN changesets in Trac tickets == |
| | 210 | |
| | 211 | 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: |
| | 212 | * '''Refs #123''' - to reference this changeset in #123 ticket |
| | 213 | * '''Fixes #123''' - to reference this changeset and close #123 ticket with the default status ''fixed'' |
| | 214 | |
| | 215 | 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. |
| | 216 | |
| | 217 | 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: |
| | 218 | |
| | 219 | {{{ |
| | 220 | $ cd /path/to/svn/repository/hooks |
| | 221 | $ mv post-commit.tmpl post-commit |
| | 222 | $ chmod 755 post-commit |
| | 223 | }}} |
| | 224 | |
| | 225 | 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: |
| | 226 | |
| | 227 | {{{ |
| | 228 | REPOS="$1" |
| | 229 | REV="$2" |
| | 230 | TRAC_ENV="/path/to/your/trac/project" |
| | 231 | |
| | 232 | /usr/bin/python /usr/local/bin/trac-post-commit-hook -p "$TRAC_ENV" -r "$REV" |
| | 233 | }}} |
| | 234 | |
| | 235 | 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]. |
| | 236 | |
| | 237 | |
| | 238 | == Platform-specifics installations == |
| | 239 | |
| | 240 | * See [trac:TracInstallPlatforms TracInstallPlatforms] |
| | 241 | |
