Trac Installation Guide
Table of Contents
Trac is a lightweight project management tool that is implemented as a web-based application. Trac is written in the Python programming language and needs a database (either SQLite, PostgreSQL, or MySQL works). For HTML rendering, Trac uses the ClearSilver templating system.
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.
To install Trac, the following software packages must be installed:
- Python, version >= 2.3
- if using mod_python together with xml-related things (like 0.11, or xml-rpc plugin), use python-2.5. expat is namespaced there and does not cause apache to crash any more(see here for details).
- For RPM-based systems you might also need the python-devel and python-xml packages.
- Please make sure to get at least ClearSilver 10.4 if you have Python 2.5.
ClearSilver up to 10.3 and Python 2.5 don't seem to get along, so you'll probably have more luck with Python 2.4. Note about it in this mail exchange.
To follow-up on that thread, with Trac 0.11dev (i.e. current trunk since r3832), Clearsilver is no longer needed. Yay. See instructions in TracOnWindows/Python2.5?
- You can fix the problem with Python 2.5 (x_64) relatively easily because Clearsilver installed neo_cgi.so in the path /usr/lib/python2.5/site-packages instead of /usr/lib64/python2.5/site-packages. To solve the problem, make a link in /usr/lib64/python2.5/site-packages with ln -s /usr/lib/python2.5/site-packages/neo_cgi.so neo_cgi.so or just move the file to the correct location.
- You also need a database system and the corresponding python drivers for it. The database can be either SQLite, PostgreSQL or MySQL (experimental).
- For 0.11dev:
- ClearSilver, version >= 0.9.3
- With python-bindings (./configure --with-python=/usr/bin/python)
- Version 10.4 required for Python 2.5
- No longer required by Trac core starting with 0.11dev… although some plugins may still require it
- SQLite, version 3.3.4 and above preferred.
- 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
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.
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". 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).
Note: PostgreSQL support requires Trac version 0.9 or later.
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 MySqlDb for more detailed informations.
Note: MySQL support requires Trac version 0.10 or later.
Version Control System
Please note: if using Subversion, Trac must be installed on the same machine. Remote repositories are not currently supported.
- Subversion, version >= 1.0. (versions recommended: 1.2.4, 1.3.2 or 1.4.0) and the corresponding Python bindings. For troubleshooting, check TracSubversion
- Trac uses the SWIG bindings included in the Subversion distribution, not PySVN (which is sometimes confused with the standard SWIG bindings).
- 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.
- There are pre-compiled bindings available for win32.
- Support for other version control systems is provided via third-parties. See PluginList and VersioningSystemBackend.
- A CGI-capable web server (see TracCgi), or
- a FastCGI-capable web server (see TracFastCgi), or
- Apache with mod_python 3.1.3+ (see TracModPython)
- When installing mod_python the development versions of Python and Apache are required (actually the libraries and header files)
- Apache with mod_wsgi (see TracModWSGI?)
- While mod_wsgi is very new and somewhat experimental, this should work with Apache 1.3, 2.0 or 2.2 and promises to deliver more performance than using mod_python.
Other Python Utilities
- setuptools, version >= 0.6 for using plugins (see TracPlugins)
- No longer optional starting with 0.11dev
- docutils, version >= 0.3.9 for WikiRestructuredText.
- SilverCity and/or Enscript for syntax highlighting.
- Note that SilverCity 0.9.6 has a bug that breaks Python syntax highlighting in Trac. Until an update is made available, we recommend using version 0.9.5.
- Note that SilverCity 0.9.7 marks the bug listed above - Fixed!
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.
Please refer to the documentation of these packages to find out how they are best installed. In addition, most of the 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!).
Like most Python programs, the Trac Python package is installed by running the following command at the top of the source directory (you must issue this command from the source directory; the installation will not work properly if you run setup.py from a different directory) :
$ python ./setup.py install
Note: you'll need root permissions or equivalent for this step.
This will byte-compile the python source code and install it in the site-packages directory of your Python installation. The directories cgi-bin, templates, htdocs, wiki-default and wiki-macros are all copied to $prefix/share/trac/. conf and plugins stub directories are also created under $prefix/share/trac/ (since 0.10).
To install Trac to a custom location, or find out about other advanced installation options, run:
$ python ./setup.py install --help
Also see Installing Python Modules for detailed information.
Specifically, you might be interested in:
$ python ./setup.py install --prefix=/path/to/installdir
Creating a Project Environment
A 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.
A new environment is created using trac-admin:
$ trac-admin /path/to/myproject initenv
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 source code repository, the 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.
Also note that the values you specify here can be changed later by directly editing the TracIni configuration file.
Note: The user account under which the web server runs will require write permissions to the environment directory and all the files inside.
Running the Standalone Server
After having created a Trac environment, you can easily try the web interface by running the standalone server tracd:
$ tracd --port 8000 /path/to/myproject
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.
Running Trac on a Web Server
If you're not afraid of running development code, you can also try running Trac on mod_wsgi?. This should deliver even better performance than mod_python, but the module is not considered stable just yet.
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 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:
- TracStandalone if you use the standalone server, tracd.
- TracCgi if you use the CGI or FastCGI methods.
- TracModPython if you use the mod_python method.
Once you have your Trac site up and running, you should be able to browse your subversion repository, create tickets, view the timeline, etc.
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 permissions to authenticated users to see the full set of features.