Changes between Initial Version and Version 1 of TracInstall

7/22/2007 8:33:50 PM (17 years ago)



  • TracInstall

    v1 v1  
     1= Trac Installation Guide =  
     4Trac 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. 
     6What 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. 
     8== Requirements == 
     10To install Trac, the following software packages must be installed: 
     12 * [ Python], version >= 2.3. 
     13   * For RPM-based systems you might also need the `python-devel` and `python-xml` packages. 
     14   * If you want to use Trac with Subversion on Windows, note that there are no precompiled Subversion bindings for Python 2.4, so you probably need Python 2.3. 
     15    * 2006-09-20: This seems to be no longer true, see For subversion 1.4.0 python 2.4 binary bindings are available. 
     16 * [ ClearSilver], version >= 0.9.3 
     17   * With python-bindings (`./configure --with-python=/usr/bin/python`) 
     18 * You also need a database system and the corresponding python drivers for it. 
     19   The database can be either SQLite, PostgreSQL or MySQL ''(experimental)''. 
     21=== For SQLite === 
     23 * [ SQLite], version 2.8.x or 3.x (preferred) 
     24 * [ PySQLite], version 1.x (for SQLite 2.x) or version 2.x (for SQLite 3.x). For details see [ PySqlite] 
     26''Note: Versions of Trac prior to 0.9 do '''not''' work with PySQLite 2.x.'' 
     28''Note: It appears that PySQLite 2.x is required for Trac 0.9+/SQLite 3.x if you plan to use the '' script available from the 'contrib' section of the source repository.'' 
     30''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).'' 
     32=== For PostgreSQL === 
     34 * [ PostgreSQL] 
     35 * [ psycopg2] or [ pyPgSQL] 
     37''Note: PostgreSQL support requires Trac version 0.9 or later.'' 
     39=== For MySQL === 
     41'''Warning''': MySQL support is currently experimental. That means it works for some people, but has not been tested extensively yet. 
     43 * [ MySQL], version 4.1 or later 
     44 * [ MySQLdb], version 1.2.1 or later 
     46''Note: MySQL support requires Trac version 0.10 or later.'' 
     48=== Optional Requirements === 
     50==== Version Control System ==== 
     51 * [ Subversion], version >= 1.0. (either 1.2.3 or >= 1.3.1 recommended) and corresponding [ Python bindings]. For troubleshooting, check [ TracSubversion] 
     52   * Trac uses the [ SWIG] bindings included in the Subversion distribution, '''not''' [ PySVN] (which is sometimes confused with the standard SWIG bindings). 
     53   * If Subversion was already installed without the SWIG bindings, you'll need to re-`configure` Subversion and `make swig-py`, `make install-swig-py`. 
     54 * Support for other version control systems is provided via third-parties. See [ PluginList] and [ VersioningSystemBackend]. 
     56==== Web Server ==== 
     57 * A CGI-capable web server (see TracCgi), or 
     58 * a [ FastCGI]-capable web server (see TracFastCgi), or 
     59 * [ Apache] with [ mod_python 3.1.3+] (see TracModPython) 
     60    * When installing mod_python the development versions of Python and Apache are required (actually the libraries and header files) 
     62For those stuck with Apache 1.3, it is also possible to get Trac 0.8.4 working with [ mod_python 2.7] (see [wiki:TracModPython2.7 TracModPython2.7]). This hasn't been tested with Trac 0.9, so it may or may not work. 
     64==== Other Python Utilities ==== 
     65 * [ setuptools], version >= 0.6 for using plugins (see TracPlugins) 
     66 * [ docutils], version >= 0.3.9 for WikiRestructuredText. 
     67 * [ SilverCity] and/or [ Enscript] for [wiki:TracSyntaxColoring syntax highlighting]. 
     68    * 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. 
     70'''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]. 
     72Please 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 might concern older versions of Trac than the one you're installing (in particular,  
     73there are still some pages that are about Trac 0.8). 
     75== Installing Trac == 
     77Like most Python programs, the Trac Python package is installed by running the following command at the top of the source directory: 
     79$ python ./ install 
     82''Note: you'll need root permissions or equivalent for this step.'' 
     84This will byte-compile the python source code and install it in the `site-packages` directory 
     85of 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 [milestone:0.10]''). 
     87The 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. 
     89=== Advanced Options === 
     91To install Trac to a custom location, or find out about other advanced installation options, run: 
     93$ python ./ install --help 
     96Also see [ Installing Python Modules] for detailed information. 
     98Specifically, you might be interested in: 
     100$ python ./ install --prefix=/path/to/installdir 
     103== Creating a Project Environment == 
     105A [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. 
     107A new environment is created using [wiki:TracAdmin trac-admin]: 
     109$ trac-admin /path/to/myproject initenv 
     112[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. 
     114Also note that the values you specify here can be changed later by directly editing the [wiki:TracIni] configuration file. 
     116''Note: The user account under which the web server runs will require write permissions to the environment 
     117directory and all the files inside.'' 
     120== Running the Standalone Server == 
     122After having created a Trac environment, you can easily try the web interface by running the standalone server [wiki:TracStandalone tracd]: 
     124$ tracd --port 8000 /path/to/myproject 
     127Then, 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. 
     130== Running Trac on a Web Server == 
     132Trac 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. 
     134== Configuring Authentication == 
     136The 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: 
     138 * TracStandalone if you use the standalone server, `tracd`. 
     139 * TracCgi if you use the CGI or FastCGI methods. 
     140 * TracModPython if you use the mod_python method. 
     142== Using Trac == 
     144Once you have your Trac site up and running, you should be able to browse your subversion repository, create tickets, view the timeline, etc. 
     146Keep 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. 
     148'' Enjoy! '' 
     150[ The Trac Team] 
     153See also:  TracGuide, TracCgi, TracFastCgi, TracModPython, TracUpgrade, TracPermissions