Changes between Version 1 and Version 2 of TracInstall
- Timestamp:
- 12/04/2008 10:18:44 PM (16 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
TracInstall
v1 v2 1 = Trac Installation Guide =1 = Trac Installation Guide for 0.11 = 2 2 [[TracGuideToc]] 3 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.4 Trac is written in the Python programming language and needs a database, [http://sqlite.org/ SQLite], [http://www.postgresql.org/ PostgreSQL], or [http://mysql.com/ MySQL]. For HTML rendering, Trac uses the [http://genshi.edgewall.org Genshi] templating system. 5 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. 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 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 == 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 12 }}} 7 13 8 14 == Requirements == 15 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. 9 16 10 17 To install Trac, the following software packages must be installed: 11 18 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.19 * [http://www.python.org/ 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 [http://www.dscpl.com.au/wiki/ModPython/Articles/ExpatCausingApacheCrash here] for details). 14 21 * 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 * With python-bindings (`./configure --with-python=/usr/bin/python`) 22 * See instructions in ["TracOnWindows/Python2.5"] 23 * [http://peak.telecommunity.com/DevCenter/setuptools setuptools], version >= 0.6 24 * [http://genshi.edgewall.org/wiki/Download 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: [http://www.clearsilver.net/ ClearSilver] 20 28 21 === For SQLite===29 ==== For SQLite ==== 22 30 23 * [http://www.sqlite.org/ SQLite], version 2.8.x or 3.x 24 * [http://pysqlite.org/ PySQLite] 25 * version 1.0.x (for SQLite 2.8.x) 26 * version 1.1.x or 2.x (for SQLite 3.x) 31 * [http://www.sqlite.org/ SQLite], version 3.3.4 and above preferred (note: it is preinstalled in Python 2.5.2). 32 * 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 [trac:PySqlite PySqlite] 27 33 28 === For PostgreSQL === 34 ''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.'' 35 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}}}". [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).'' 37 38 ==== For PostgreSQL ==== 29 39 30 40 * [http://www.postgresql.org/ PostgreSQL] 31 * [http://initd.org/projects/psycopg1 psycopg1], [http://initd.org/projects/psycopg2 psycopg2], or [http://pypgsql.sourceforge.net/ pyPgSQL] 41 * [http://initd.org/projects/psycopg2 psycopg2] 42 * See [trac:wiki:DatabaseBackend#Postgresql DatabaseBackend] 32 43 33 === Optional Requirements === 44 '''Warning''': PostgreSQL 8.3 uses a strict type checking mechanism. To use Trac with the 8.3 Version of PostgreSQL, you will need [http://trac.edgewall.org/changeset/6512 trac-0.11] or later. 34 45 46 ==== For MySQL ==== 47 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. 49 50 * [http://mysql.com/ MySQL], version 4.1 or later 51 * [http://sf.net/projects/mysql-python MySQLdb], version 1.2.1 or later 52 53 == Optional Requirements == 54 55 ==== Version Control System ==== 56 57 '''Please note:''' if using Subversion, Trac must be installed on the '''same machine'''. Remote repositories are currently not supported. 58 59 * [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] 60 * Trac uses the [http://svnbook.red-bean.com/svnbook-1.1/ch08s02.html#svn-ch-8-sect-2.3 SWIG] bindings included in the Subversion distribution, '''not''' [http://pysvn.tigris.org/ 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 [http://subversion.tigris.org/servlets/ProjectDocumentList?folderID=91 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]. 64 65 ==== Web Server ==== 35 66 * A CGI-capable web server (see TracCgi), or 36 67 * a [http://www.fastcgi.com/ FastCGI]-capable web server (see TracFastCgi), or 68 * an [http://tomcat.apache.org/connectors-doc/ajp/ajpv13a.html AJP]-capable web server (see [trac:TracOnWindowsIisAjp TracOnWindowsIisAjp]), or 69 * [http://httpd.apache.org/ Apache] with [http://code.google.com/p/modwsgi/ mod_wsgi] (see [wiki:TracModWSGI] or http://code.google.com/p/modwsgi/wiki/IntegrationWithTrac) 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. 37 71 * [http://httpd.apache.org/ Apache] with [http://www.modpython.org/ mod_python 3.1.3+] (see TracModPython) 38 * [http://peak.telecommunity.com/DevCenter/setuptools setuptools], version >= 0.5a13 for using plugins (see TracPlugins) 39 * [http://docutils.sourceforge.net/ docutils], version >= 0.3.3 for WikiRestructuredText. 40 * [http://silvercity.sourceforge.net/ SilverCity] and/or [http://www.gnu.org/software/enscript/enscript.html Enscript] for [wiki:TracSyntaxColoring syntax highlighting]. 72 * When installing mod_python the development versions of Python and Apache are required (actually the libraries and header files) 41 73 42 '''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].74 For those stuck with Apache 1.3, it is also possible to get Trac working with [http://www.modpython.org/ 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. 43 75 44 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. 76 ==== Other Python Utilities ==== 77 * [http://docutils.sourceforge.net/ docutils], version >= 0.3.9 for WikiRestructuredText. 78 * [http://pygments.pocoo.org Pygments] for '''syntax highlighting''', although [http://silvercity.sourceforge.net/ SilverCity] >= 0.9.7 and/or [http://gnu.org/software/enscript/enscript.html GNU Enscript] are also possible. Refer to TracSyntaxColoring for details. 79 * [http://pytz.sf.net pytz] to get a complete list of time zones, otherwise Trac will fall back on a shorter list from an internal time zone implementation. 80 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]. 82 83 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!). 45 84 46 85 == Installing Trac == 47 86 48 Like most Python programs, the Trac Python package is installed by running the following command at the top of the source directory: 87 One way to install Trac is using `setuptools`. 88 With setuptools you can install Trac from the subversion repository; for example, 89 to install release version 0.11 do: 90 {{{ 91 easy_install http://svn.edgewall.org/repos/trac/tags/trac-0.11 92 }}} 93 94 But of course the python-typical setup at the top of the source directory also works: 49 95 {{{ 50 96 $ python ./setup.py install … … 53 99 ''Note: you'll need root permissions or equivalent for this step.'' 54 100 55 This will byte-compile the python source code and install it in the `site-packages` directory56 of your Python installation. The directories `cgi-bin`, `templates`, `htdocs`, `wiki-default` and `wiki-macros` are all copied to `$prefix/share/trac/.`101 This will byte-compile the python source code and install it as an .egg file or folder in the `site-packages` directory 102 of your Python installation. The .egg will also contain all other resources needed by standard Trac, such as htdocs and templates. 57 103 58 104 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. 59 105 60 === Advanced Users===106 ==== Advanced Options ==== 61 107 62 108 To install Trac to a custom location, or find out about other advanced installation options, run: 63 109 {{{ 64 $ python ./setup.py--help110 easy_install --help 65 111 }}} 112 113 Also see [http://docs.python.org/inst/inst.html Installing Python Modules] for detailed information. 66 114 67 115 Specifically, you might be interested in: 68 116 {{{ 69 $ python ./setup.py install --prefix=/path/you/want 117 easy_install --prefix=/path/to/installdir 118 }}} 119 or, if installing Trac to a Mac OS X system: 120 {{{ 121 easy_install --prefix=/usr/local --install-dir=/Library/Python/2.5/site-packages 70 122 }}} 71 123 124 The 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. 72 125 73 126 == Creating a Project Environment == … … 77 130 A new environment is created using [wiki:TracAdmin trac-admin]: 78 131 {{{ 79 $ trac-admin /path/to/ trac_project_envinitenv132 $ trac-admin /path/to/myproject initenv 80 133 }}} 81 134 82 [wiki:TracAdmin trac-admin] will prompt you for the information it needs to create the environment, such as the name of the project, the path to an existing subversion 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. 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.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. 83 136 84 137 Also note that the values you specify here can be changed later by directly editing the [wiki:TracIni] configuration file. 85 138 86 ''Note: The user account under which the web server runs will require write permissions to the environment 87 directory and all the files inside.'' 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:'' 88 140 141 chown -R apache.apache /path/to/myproject 142 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 http://trac.edgewall.org/ticket/7312 and possibly http://trac.edgewall.org/ticket/6827''' 89 144 90 145 == Running the Standalone Server == … … 92 147 After having created a Trac environment, you can easily try the web interface by running the standalone server [wiki:TracStandalone tracd]: 93 148 {{{ 94 $ tracd --port 8000 /path/to/ projectenv149 $ tracd --port 8000 /path/to/myproject 95 150 }}} 96 151 97 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. 152 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. 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: 153 {{{ 154 $ tracd -s --port 8000 /path/to/myproject 155 }}} 98 156 99 157 100 158 == Running Trac on a Web Server == 101 159 102 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. 160 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. 161 162 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. 163 164 Trac also supports [trac:TracOnWindowsIisAjp AJP] which may be your choice if you want to connect to IIS. 165 166 ==== Setting up the Plugin Cache ==== 167 168 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. 103 169 104 170 == Configuring Authentication == 105 171 106 The process of adding, removing, and configuring user accounts for authentication depends on the specific way you run Trac. To learn about how to accomplish these tasks, please visitone of the following pages:172 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 [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: 107 173 108 174 * TracStandalone if you use the standalone server, `tracd`. 109 175 * TracCgi if you use the CGI or FastCGI methods. 110 176 * TracModPython if you use the mod_python method. 177 178 == Trac 0.11 & SVN on Mac OS X Leopard (10.5) == 179 180 * [trac:TracOnLeopardServer TracOnLeopardServer] 111 181 112 182 == Using Trac == … … 116 186 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. 117 187 118 '' Enjoy!''188 '' Enjoy! '' 119 189 120 [ http://projects.edgewall.com/trac/wiki/TracTeam The Trac Team]190 [trac:TracTeam The Trac Team] 121 191 122 192 ---- 123 See also: TracGuide, TracCgi, TracFastCgi, TracModPython, TracUpgrade, TracPermissions 193 See also: TracGuide, TracCgi, TracFastCgi, TracModPython, [wiki:TracModWSGI], TracUpgrade, TracPermissions 194