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.

8

9

See TracUpgrade for instructions on how to upgrade an existing installation.

10

11

12

== Quick Install a Released Version ==

13

For a quick install, first make sure you have [http://python.org/download Python] (2.3-2.6) and [http://peak.telecommunity.com/DevCenter/EasyInstall#installing-easy-install easy_install].

14

15

Then enter (''omitting 'sudo' if not applicable'')

16

{{{

17

sudo easy_install Trac

18

}}}

19

to install Trac, SQLite, and Genshi.

20

21

22

== Requirements ==

23

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.

24

25

To install Trac, the following software packages must be installed:

26

27

* [http://www.python.org/ Python], version >=2.3 (<3.0)

28

* 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).

29

* For RPM-based systems you might also need the `python-devel` and `python-xml` packages.

30

* See instructions in [trac:wiki:TracOnWindows/Python2.5 TracOnWindows/Python2.5]

That way, the latest SQLite version will be downloaded and built into the

51

bindings.

52

53

If you're still using SQLite 2.x, you'll need pysqlite 1.0.x, although this

54

package is not easy to find anymore. For SQLite 3.x, try not to use

55

pysqlite 1.1.x, which has been deprecated in favor of pysqlite 2.x.

56

57

See additional information in [trac:PySqlite PySqlite].

58

59

==== For PostgreSQL ====

60

61

* [http://www.postgresql.org/ PostgreSQL]

62

* [http://initd.org/projects/psycopg2 psycopg2]

63

* See [trac:wiki:DatabaseBackend#Postgresql DatabaseBackend]

64

65

'''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.

66

67

==== For MySQL ====

68

69

* [http://mysql.com/ MySQL], version 4.1 or later ([http://askmonty.org/wiki/index.php/MariaDB MariaDB] might work as well)

70

* [http://sf.net/projects/mysql-python MySQLdb], version 1.2.1 or later

71

72

See [trac:MySqlDb MySqlDb] for more detailed information.

73

It is ''very'' important to read carefully that page before creating the database.

74

75

== Optional Requirements ==

76

77

==== Version Control System ====

78

79

'''Please note:''' if using Subversion, Trac must be installed on the '''same machine'''. Remote repositories are currently not supported (although Windows UNC paths such as {{{\\machine_name\path\to\svn}}} do work).

* When installing mod_python the development versions of Python and Apache are required (actually the libraries and header files)

95

96

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 [trac:wiki:TracModPython2.7 TracModPython2.7]). This guide hasn't been updated since 0.84, so it may or may not work.

* [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.

102

103

'''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].

104

105

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!).

106

107

== Installing Trac ==

108

109

One way to install Trac is using `setuptools`.

110

With setuptools you can install Trac from the subversion repository; for example,

111

to install release version 0.11 do:

112

{{{

113

easy_install http://svn.edgewall.org/repos/trac/tags/trac-0.11

114

}}}

115

116

But of course the python-typical setup at the top of the source directory also works:

117

{{{

118

$ python ./setup.py install

119

}}}

120

121

''Note: you'll need root permissions or equivalent for this step.''

122

123

This will byte-compile the python source code and install it as an .egg file or folder in the `site-packages` directory

124

of your Python installation. The .egg will also contain all other resources needed by standard Trac, such as htdocs and templates.

125

126

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.

127

128

==== Advanced Options ====

129

130

To install Trac to a custom location, or find out about other advanced installation options, run:

131

{{{

132

easy_install --help

133

}}}

134

135

Also see [http://docs.python.org/inst/inst.html Installing Python Modules] for detailed information.

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.

147

148

== Creating a Project Environment ==

149

150

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.

151

152

A new environment is created using [wiki:TracAdmin trac-admin]:

153

{{{

154

$ trac-admin /path/to/myproject initenv

155

}}}

156

157

[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.

158

159

Also note that the values you specify here can be changed later by directly editing the [wiki:TracIni] configuration file.

160

161

''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:''

162

163

chown -R apache.apache /path/to/myproject

164

165

== Running the Standalone Server ==

166

167

After having created a Trac environment, you can easily try the web interface by running the standalone server [wiki:TracStandalone tracd]:

168

{{{

169

$ tracd --port 8000 /path/to/myproject

170

}}}

171

172

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:

173

{{{

174

$ tracd -s --port 8000 /path/to/myproject

175

}}}

176

177

== Running Trac on a Web Server ==

178

179

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.

180

181

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.

182

183

Trac also supports [trac:TracOnWindowsIisAjp AJP] which may be your choice if you want to connect to IIS.

184

185

==== Generating the Trac cgi-bin directory ====

186

187

In order for Trac to function properly with FastCGI or mod_python, you need to have a trac.cgi file. This is an executable which loads the appropriate Python code. It can be generated using the `deploy` option of [wiki:TracAdmin trac-admin].

188

189

There is, however, a bit of a chicken-and-egg problem. The [wiki:TracAdmin trac-admin] command requires an existing environment to function, but complains if the deploy directory already exists. This is a problem, because environments are often stored in a subdirectory of the deploy. The solution is to do something like this:

190

{{{

191

mkdir -p /usr/share/trac/projects/my-project

192

trac-admin /usr/share/trac/projects/my-project initenv

193

trac-admin /usr/share/trac/projects/my-project deploy /tmp/deploy

194

mv /tmp/deploy/* /usr/share/trac

195

}}}

196

197

==== Setting up the Plugin Cache ====

198

199

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.

200

201

== Configuring Authentication ==

202

203

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:

204

205

* TracStandalone if you use the standalone server, `tracd`.

206

* TracCgi if you use the CGI or FastCGI methods.

207

* TracModPython if you use the mod_python method.

208

209

== Automatic reference to the SVN changesets in Trac tickets ==

210

211

You can configure SVN to automatically add a reference to the changeset into the ticket comments, whenever files are committed to the repository. The description of the commit needs to contain one of the following formulas:

212

* '''Refs #123''' - to reference this changeset in #123 ticket

213

* '''Fixes #123''' - to reference this changeset and close #123 ticket with the default status ''fixed''

214

215

All you have to do is to edit the ''post-commit'' hook in your SVN repository and make it execute ''trac-post-commit-hook'' coming with Trac.

216

217

If you are editing the ''post-commit'' hook for the first time you need to navigate to your SVN repository's hooks subfolder and rename existing there ''post-commit'' template:

218

219

{{{

220

$ cd /path/to/svn/repository/hooks

221

$ mv post-commit.tmpl post-commit

222

$ chmod 755 post-commit

223

}}}

224

225

Next open it in any text editor and add a line with path to the Trac environment connected with this SVN repository and another line executing the ''trac-post-commit-hook'' script:

Make sure that ''trac-post-commit-hook'' exists in above path with execution permissions for the same user which SVN is running from. This script can be found in contrib subfolder of your Trac distribution and the latest version can be always downloaded from [source:trunk/contrib/trac-post-commit-hook].

236

237

238

== Platform-specifics installations ==

239

240

* See [trac:TracInstallPlatforms TracInstallPlatforms]

241

242

243

== Using Trac ==

244

245

Once you have your Trac site up and running, you should be able to browse your subversion repository, create tickets, view the timeline, etc.

246

247

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.