| 1 | = Trac Installation Guide = |
| 2 | [[TracGuideToc]] |
| 3 | |
| 4 | Trac is a lightweight project management tool that is implemented as a web-based application. Trac is written in the Python programming language and can use [http://sqlite.org/ SQLite] or [http://www.postgresql.org/ PostgreSQL] as database. For HTML rendering, Trac uses the [http://www.clearsilver.net/ Clearsilver] templating system. |
| 5 | |
| 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 [http://projects.edgewall.com/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. |
| 7 | |
| 8 | == Requirements == |
| 9 | |
| 10 | To install Trac, the following software packages must be installed: |
| 11 | |
| 12 | * [http://www.python.org/ Python], version >= 2.3. |
| 13 | * Python 2.4 is not supported on Windows since there are no Subversion bindings available for it. |
| 14 | * For RPM-based systems you might also need the `python-devel` and `python-xml` packages. |
| 15 | * [http://subversion.tigris.org/ Subversion], version >= 1.0. (>= 1.1 recommended) and corresponding [http://svnbook.red-bean.com/svnbook-1.1/ch08s02.html#svn-ch-8-sect-2.3 Python bindings] |
| 16 | * Trac uses the [http://www.swig.org/ SWIG] bindings included in the Subversion distribution, '''not''' [http://pysvn.tigris.org/ PySVN] (which is sometimes confused with the standard SWIG bindings). |
| 17 | * If Subversion was already installed without the SWIG bindings, you'll need to re-`configure` Subversion and `make swig-py`, `make install-swig-py`. |
| 18 | * [http://www.clearsilver.net/ ClearSilver], version >= 0.9.3 |
| 19 | |
| 20 | === For SQLite === |
| 21 | |
| 22 | * [http://www.sqlite.org/ SQLite], version 2.8.x or 3.x |
| 23 | * [http://pysqlite.org/ PySQLite] |
| 24 | * version 1.0.x (for SQLite 2.8.x) |
| 25 | * version 1.1.x or 2.x (for SQLite 3.x) |
| 26 | |
| 27 | ''Note: Versions of Trac prior to 0.9 do '''not''' work with PySQLite 2.x.'' |
| 28 | |
| 29 | === For PostgreSQL === |
| 30 | |
| 31 | * [http://www.postgresql.org/ PostgreSQL] |
| 32 | * [http://initd.org/projects/psycopg1 psycopg1], [http://initd.org/projects/psycopg2 psycopg2], or [http://pypgsql.sourceforge.net/ pyPgSQL] |
| 33 | |
| 34 | ''Note: PostgreSQL support requires Trac version 0.9 or later.'' |
| 35 | |
| 36 | === Optional Requirements === |
| 37 | |
| 38 | * A CGI-capable web server (see TracCgi), or |
| 39 | * a [http://www.fastcgi.com/ FastCGI]-capable web server (see TracFastCgi), or |
| 40 | * [http://httpd.apache.org/ Apache] with [http://www.modpython.org/ mod_python 3.1.3+] (see TracModPython) |
| 41 | * [http://docutils.sourceforge.net/ docutils], version >= 0.3.3 for WikiRestructuredText. |
| 42 | * [http://peak.telecommunity.com/DevCenter/setuptools setuptools], version >= 0.5a13 for using plugins (see TracPlugins) |
| 43 | |
| 44 | '''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 [http://projects.edgewall.com/trac/wiki/MailingList MailingList] or [http://projects.edgewall.com/trac/wiki/IrcChannel IrcChannel]. |
| 45 | |
| 46 | Please refer to the documentation of these packages to find out how they are best installed. In addition, most of the [http://projects.edgewall.com/trac/wiki/TracInstallPlatforms platform-specific instructions] also describe the installation of the dependencies. |
| 47 | |
| 48 | == Installing Trac == |
| 49 | |
| 50 | Like most Python programs, install the Trac Python package by running the following command at the top of the source directory: |
| 51 | {{{ |
| 52 | $ python ./setup.py install |
| 53 | }}} |
| 54 | |
| 55 | ''Note: you'll need root permissions or equivalent for this step.'' |
| 56 | |
| 57 | This will byte-compile the python source code and install it in the `site-packages` directory |
| 58 | of your Python installation. The directories `cgi-bin`, `templates`, `htdocs` and `wiki-default` are all copied to `$prefix/share/trac/.` |
| 59 | |
| 60 | 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. |
| 61 | |
| 62 | === Advanced Users === |
| 63 | |
| 64 | To install Trac to a custom location, or find out about other advanced installation options, run: |
| 65 | {{{ |
| 66 | $ python ./setup.py --help |
| 67 | }}} |
| 68 | |
| 69 | Specifically, you might be interested in: |
| 70 | {{{ |
| 71 | $ python ./setup.py install --prefix=/path/you/want |
| 72 | }}} |
| 73 | |
| 74 | |
| 75 | == Creating a Project Environment == |
| 76 | |
| 77 | A [wiki: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 configuration file and various other files and directories. |
| 78 | |
| 79 | A new environment is created using [wiki:TracAdmin trac-admin]: |
| 80 | {{{ |
| 81 | $ svnadmin create --fs-type=fsfs /path/to/svn_project_env |
| 82 | (in some environments leave out the parameters "--fs-type=fsfs" ) |
| 83 | $ trac-admin /path/to/trac_project_env initenv |
| 84 | }}} |
| 85 | |
| 86 | [wiki:TracAdmin trac-admin] will prompt you for the information it needs to create the environment, such as the name of the project, 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. The only option where the default value is likely to not work is the path to the Subversion repository, so make sure that one's correct. |
| 87 | |
| 88 | Also note that the values you specify here can be changed later by directly editing the [wiki:TracIni] configuration file. |
| 89 | |
| 90 | ''Note: The user account under which the web server runs will require write permissions to the environment |
| 91 | directory and all the files inside.'' |
| 92 | |
| 93 | |
| 94 | == Running the Standalone Server == |
| 95 | |
| 96 | After having created a Trac environment, you can easily try the web interface by running the standalone server [wiki:TracStandalone tracd]: |
| 97 | {{{ |
| 98 | $ tracd --port 8000 /path/to/projectenv |
| 99 | }}} |
| 100 | |
| 101 | Then, fire up a browser and visit `http://localhost:8000/`. You should get a simple listing of all environments that tracd knows about. Follow the link to the environment you just created, and you should see Trac in action. |
| 102 | |
| 103 | |
| 104 | == Running Trac on a Web Server == |
| 105 | |
| 106 | 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. |
| 107 | |
| 108 | |
| 109 | == Using Trac == |
| 110 | |
| 111 | Once you have your Trac site up and running, you should be able to browse your subversion repository, create tickets, view the timeline, etc. |
| 112 | |
| 113 | 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. |
| 114 | |
| 115 | ''Enjoy!'' |
| 116 | |
| 117 | [http://projects.edgewall.com/trac/wiki/TracTeam The Trac Team] |
| 118 | |
| 119 | ---- |
| 120 | See also: TracGuide, TracCgi, TracFastCgi, TracModPython, TracUpgrade, TracPermissions |