Changes between Initial Version and Version 1 of TracInstall

09/01/10 13:25:58 (12 years ago)



  • TracInstall

    v1 v1  
     1= Trac Installation Guide for 0.11 =  
     4Trac is written in the Python programming language and needs a database, [ SQLite], [ PostgreSQL], or [ MySQL]. For HTML rendering, Trac uses the [ Genshi] 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== Short - Install a released version == 
     9For the quick install, make sure you have [ Python-2.5], [ easy_install] and SQlite-3.3.4 installed (or above). 
     11sudo easy_install Trac 
     14== Requirements == 
     15The 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. 
     17To install Trac, the following software packages must be installed: 
     19 * [ Python], version >= 2.3 
     20   * if using mod_python together with xml-related things, use python-2.5. expat is namespaced there and does not cause apache to crash any more(see [ here] for details). 
     21   * For RPM-based systems you might also need the `python-devel` and `python-xml` packages. 
     22   * See instructions in ["TracOnWindows/Python2.5"] 
     23 * [ setuptools], version >= 0.6 
     24 * [ 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: [ ClearSilver] 
     29==== For SQLite ==== 
     31 * [ SQLite], version 3.3.4 and above preferred (note: it is preinstalled in Python 2.5.2). 
     32 * If not using Python-2.5: [ 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] 
     34''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.'' 
     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}}}". [ 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).'' 
     38==== For PostgreSQL ==== 
     40 * [ PostgreSQL] 
     41 * [ psycopg2] 
     42 * See [trac:wiki:DatabaseBackend#Postgresql DatabaseBackend] 
     44'''Warning''': PostgreSQL 8.3 uses a strict type checking mechanism. To use Trac with the 8.3 Version of PostgreSQL, you will need [ trac-0.11] or later. 
     46==== For MySQL ==== 
     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. 
     50 * [ MySQL], version 4.1 or later 
     51 * [ MySQLdb], version 1.2.1 or later 
     53== Optional Requirements == 
     55==== Version Control System ==== 
     57'''Please note:''' if using Subversion, Trac must be installed on the '''same machine'''. Remote repositories are currently not supported. 
     59 * [ 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 [ SWIG] bindings included in the Subversion distribution, '''not''' [ 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 [ 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]. 
     65==== Web Server ==== 
     66 * A CGI-capable web server (see TracCgi), or 
     67 * a [ FastCGI]-capable web server (see TracFastCgi), or 
     68 * an [ AJP]-capable web server (see [trac:TracOnWindowsIisAjp TracOnWindowsIisAjp]), or 
     69 * [ Apache] with [ mod_wsgi] (see [wiki:TracModWSGI] or 
     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 * [ Apache] with [ 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) 
     74For those stuck with Apache 1.3, it is also possible to get Trac working with [ 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. 
     76==== Other Python Utilities ==== 
     77 * [ docutils], version >= 0.3.9 for WikiRestructuredText. 
     78 * [ Pygments] for '''syntax highlighting''', although [ SilverCity] >= 0.9.7 and/or [ GNU Enscript] are also possible. Refer to TracSyntaxColoring for details. 
     79 * [ pytz] to get a complete list of time zones, otherwise Trac will fall back on a shorter list from an internal time zone implementation. 
     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]. 
     83Please 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!). 
     85== Installing Trac == 
     87One way to install Trac is using `setuptools`. 
     88With setuptools you can install Trac from the subversion repository; for example, 
     89to install release version 0.11 do: 
     94But of course the python-typical setup at the top of the source directory also works: 
     96$ python ./ install 
     99''Note: you'll need root permissions or equivalent for this step.'' 
     101This will byte-compile the python source code and install it as an .egg file or folder in the `site-packages` directory 
     102of your Python installation. The .egg will also contain all other resources needed by standard Trac, such as htdocs and templates. 
     104The 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. 
     106==== Advanced Options ==== 
     108To install Trac to a custom location, or find out about other advanced installation options, run: 
     110easy_install --help 
     113Also see [ Installing Python Modules] for detailed information. 
     115Specifically, you might be interested in: 
     117easy_install --prefix=/path/to/installdir 
     119or, if installing Trac to a Mac OS X system: 
     121easy_install --prefix=/usr/local --install-dir=/Library/Python/2.5/site-packages 
     124The above will place your `tracd` and `trac-admin` commands into `/usr/local/bin` and will install the Trac libraries and dependencies into `/Library/Python/2.5/site-packages`, which is Apple's preferred location for third-party Python application installations. 
     126== Creating a Project Environment == 
     128A [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. 
     130A new environment is created using [wiki:TracAdmin trac-admin]: 
     132$ trac-admin /path/to/myproject initenv 
     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. 
     137Also note that the values you specify here can be changed later by directly editing the [wiki:TracIni] configuration file. 
     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:'' 
     141  chown -R apache.apache /path/to/myproject 
     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 and possibly''' 
     145== Running the Standalone Server == 
     147After having created a Trac environment, you can easily try the web interface by running the standalone server [wiki:TracStandalone tracd]: 
     149$ tracd --port 8000 /path/to/myproject 
     152Then, 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. If you only plan on managing a single project with trac you can have the standalone server skip the environment list by starting it like this: 
     154$ tracd -s --port 8000 /path/to/myproject 
     158== Running Trac on a Web Server == 
     160Trac 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. 
     162If 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. 
     164Trac also supports [trac:TracOnWindowsIisAjp AJP] which may be your choice if you want to connect to IIS. 
     166==== Setting up the Plugin Cache ==== 
     168Some 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. 
     170== Configuring Authentication == 
     172The 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: 
     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. 
     178== Trac 0.11 & SVN on Mac OS X Leopard (10.5) == 
     180 * [trac:TracOnLeopardServer TracOnLeopardServer] 
     182== Using Trac == 
     184Once you have your Trac site up and running, you should be able to browse your subversion repository, create tickets, view the timeline, etc. 
     186Keep 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. 
     188'' Enjoy! '' 
     190[trac:TracTeam The Trac Team] 
     193See also:  TracGuide, TracCgi, TracFastCgi, TracModPython, [wiki:TracModWSGI], TracUpgrade, TracPermissions