Changes between Version 3 and Version 4 of TracInstall


Ignore:
Timestamp:
Apr 13, 2010, 1:41:48 AM (10 years ago)
Author:
trac
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • TracInstall

    v3 v4  
    1 = Trac Installation Guide for 0.11 =
     1= Trac Installation Guide for 0.12dev =
     2{{{
     3#!div style="margin-top: .5em; padding: 0 1em; background-color: #ffd; border:1px outset #ddc;"
     4
     5  '''NOTE: this page is for 0.12dev (trunk), the version currently in development. For installing previous Trac versions, please refer to [[0.11/TracInstall]]'''
     6}}}
    27[[TracGuideToc]]
    38
    49Trac 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.
    510
    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). (You also might want to install python-dev to build genshi)
    10 {{{
    11 sudo easy_install Trac
    12 }}}
    13 
    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.
    16 
     11Since version 0.12, Trac can also be localized, and there's probably a translation available for your language. If you want to be able to use the Trac interface in other languages, then make sure you have installed the optional package [#OtherPythonPackages Babel]. Pay attention to the extra steps for localization support in the [#InstallingTrac Installing Trac] section below. Lacking Babel, you will only get the default english version, as usual.
     12
     13If you're interested in contributing new translations for other languages or enhance the existing translations, then please have a look at ["TracL10N"].
     14
     15What follows are generic instructions for installing and setting up Trac and its requirements. While you may 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.
     16
     17
     18== Dependencies ==
     19=== Mandatory Dependencies
    1720To install Trac, the following software packages must be installed:
    1821
    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).
    21    * For RPM-based systems you might also need the `python-devel` and `python-xml` packages.
    22    * See instructions in ["TracOnWindows/Python2.5"]
     22 * [http://www.python.org/ Python], version >= 2.4 and < 3.0
     23   (note that we dropped the support for Python 2.3 in this release)
    2324 * [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]
    28 
    29 ==== For SQLite ====
    30 
    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]
    33 
    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 ====
    39 
     25 * [http://genshi.edgewall.org/wiki/Download Genshi], [genshi:source:trunk trunk], from svn, minimum required revision is [G1072], current [G1092] works fine as well.
     26
     27You also need a database system and the corresponding python bindings.
     28The database can be either SQLite, PostgreSQL or MySQL.
     29
     30==== For the SQLite database #ForSQLite
     31
     32If you're using Python 2.5 or 2.6, you already have everything you need.
     33
     34If you're using Python 2.4 and need pysqlite, you can download from
     35[http://code.google.com/p/pysqlite/downloads/list google code] the Windows
     36installers or the tar.gz archive for building from source:
     37{{{
     38$ tar xvfz <version>.tar.gz
     39$ cd <version>
     40$ python setup.py build_static install
     41}}}
     42 
     43This will extract the SQLite code and build the bindings.
     44
     45SQLite 2.x is no longer supported. For SQLite 3.x, the pysqlite 1.1.x
     46bindings are also no longer supported, use pysqlite 2.x.
     47
     48See additional information in [trac:PySqlite PySqlite].
     49
     50==== For the PostgreSQL database #ForPostgreSQL
     51
     52You need to install the database and its Python bindings:
    4053 * [http://www.postgresql.org/ PostgreSQL]
    41  * [http://initd.org/projects/psycopg2 psycopg2]
    42  * See [trac:wiki:DatabaseBackend#Postgresql DatabaseBackend]
    43 
    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.
    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 * [http://pypi.python.org/pypi/psycopg2 psycopg2]
     55
     56See [trac:DatabaseBackend#Postgresql DatabaseBackend] for details.
     57
     58
     59==== For the MySQL database #ForMySQL
     60
     61Trac can now work quite well with MySQL, provided you follow the guidelines.
     62
     63 * [http://mysql.com/ MySQL], version 5.0 or later
     64 * [http://sf.net/projects/mysql-python MySQLdb], version 1.2.2 or later
     65
     66It is '''very''' important to read carefully the  [trac:MySqlDb MySqlDb] page before creating the database.
     67
     68=== Optional Dependencies
    5469
    5570==== Version Control System ====
    5671
    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].
     72===== Subversion =====
     73 * [http://subversion.apache.org/ Subversion], 1.5.x or 1.6.x and the '''''corresponding''''' Python bindings. Older versions starting from 1.0, like 1.2.4, 1.3.2 or 1.4.2, etc. should still work. For troubleshooting information, check the [trac:TracSubversion#Troubleshooting TracSubversion] page.
     74
     75There are [http://subversion.apache.org/packages.html pre-compiled SWIG bindings] available for various platforms. Note that Trac '''doesn't''' use [http://pysvn.tigris.org/ PySVN], neither does it work yet with the newer `ctype`-style bindings
     76
     77
     78'''Please note:''' if using Subversion, Trac must be installed on the '''same machine'''. Remote repositories are currently [trac:ticket:493 not supported].
     79
     80
     81===== Others =====
     82
     83Support for other version control systems is provided via third-parties. See [trac:PluginList PluginList] and [trac:VersioningSystemBackend VersioningSystemBackend].
    6484
    6585==== Web Server ====
    66  * A CGI-capable web server (see TracCgi), or
    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.
    71  * [http://httpd.apache.org/ Apache] with [http://www.modpython.org/ 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)
    73 
    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.
    75 
    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.
     86A web server is optional because Trac is shipped with a server included, see the [#RunningtheStandaloneServer Running the Standalone Server ] section below.
     87
     88Alternatively you configure Trac to run in any of the following environments.
     89 * [http://httpd.apache.org/ Apache] with
     90   - [http://code.google.com/p/modwsgi/ mod_wsgi], see [wiki:TracModWSGI] and
     91     http://code.google.com/p/modwsgi/wiki/IntegrationWithTrac
     92   - [http://modpython.org/ mod_python 3.3.1], see TracModPython)
     93 * a [http://www.fastcgi.com/ FastCGI]-capable web server (see TracFastCgi)
     94 * an [http://tomcat.apache.org/connectors-doc/ajp/ajpv13a.html AJP]-capable web
     95   server (see [trac:TracOnWindowsIisAjp TracOnWindowsIisAjp])
     96 * A CGI-capable web server (see TracCgi), '''but usage of Trac as a cgi script
     97   is highly discouraged''', better use one of the following options,
     98   
     99
     100==== Other Python Packages ====
     101
     102 * [http://babel.edgewall.org Babel], version >= 0.9.5,
     103   needed for localization support
     104 * [http://docutils.sourceforge.net/ docutils], version >= 0.3.9
     105   for WikiRestructuredText.
     106 * [http://pygments.pocoo.org Pygments] for
     107   [wiki:TracSyntaxColoring syntax highlighting].
     108   [http://silvercity.sourceforge.net/ SilverCity] and/or
     109   [http://gnu.org/software/enscript/enscript.html Enscript] may still be used
     110   but are deprecated and you really should be using Pygments.
     111 * [http://pytz.sf.net pytz] to get a complete list of time zones,
     112   otherwise Trac will fall back on a shorter list from
     113   an internal time zone implementation.
    80114
    81115'''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].
    82116
    83117Please 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!).
     118
    84119
    85120== Installing Trac ==
     
    87122One way to install Trac is using `setuptools`.
    88123With 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
     124to install release version 0.12dev do:
     125{{{
     126easy_install http://svn.edgewall.org/repos/trac/trunk
    92127}}}
    93128
     
    96131$ python ./setup.py install
    97132}}}
    98 
    99 ''Note: you'll need root permissions or equivalent for this step.''
     133See SubversionRepository for details about getting the source.
     134
     135''Note 1: you'll need root permissions or equivalent for this step.'' [[br]]
     136''Note 2: installing from source is the preferred method if you want to have a localized version of Trac'' [[br]]
    100137
    101138This will byte-compile the python source code and install it as an .egg file or folder in the `site-packages` directory
     
    104141The 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.
    105142
    106 ==== Advanced Options ====
     143If you want to make Trac available in other languages, make sure you have installed Babel and then run this additional step before doing the `install` (or simply redo the `install` afterwards):
     144{{{
     145$ python ./setup.py compile_catalog -f
     146}}}
     147(the `-f` flag is needed as long as some translations are marked ''fuzzy'', i.e. incomplete, which will most probably be the case during the whole development period, as  strings are continuously added or modified)
     148
     149
     150=== Advanced Options ===
    107151
    108152To install Trac to a custom location, or find out about other advanced installation options, run:
     
    121165easy_install --prefix=/usr/local --install-dir=/Library/Python/2.5/site-packages
    122166}}}
     167Note: If installing on Mac OS X 10.6 running {{{ easy_install http://svn.edgewall.org/repos/trac/trunk }}} will install into {{{ /usr/local }}} and {{{ /Library/Python/2.6/site-packages }}} by default
    123168
    124169The 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.
    125170
     171
    126172== Creating a Project Environment ==
    127173
    128 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.
     174A [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 [TracIni configuration file], and various other files and directories.
    129175
    130176A new environment is created using [wiki:TracAdmin trac-admin]:
     
    133179}}}
    134180
    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.
    136 
    137 Also note that the values you specify here can be changed later by directly editing the [wiki:TracIni] configuration file.
    138 
    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:''
    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'''
     181[TracAdmin trac-admin] will prompt you for the information it needs to create the environment, such as the name of the project and the [TracEnvironment#DatabaseConnectionStrings database connection string]. If you're not sure what to specify for one of these options, just press `<Enter>` to use the default value.
     182
     183Using the default database connection string in particular will always work as long as you have SQLite installed.
     184For the other [DatabaseBackend database backends] you should plan ahead and already have a database ready to use at this point.
     185
     186Since 0.12, Trac doesn't ask for a [TracEnvironment#SourceCodeRepository source code repository] anymore when creating an environment. Repositories can be [TracRepositoryAdmin added] afterward, or the version control support can be disabled completely if you don't need it.
     187
     188Also note that the values you specify here can be changed later by directly editing the [TracIni conf/trac.ini] configuration file.
     189
     190Finally, make sure the user account under which the web front-end runs will have '''write permissions''' to the environment directory and all the files inside. This will be the case if you run `trac-admin ... initenv` as this user. If not, you should set the correct user afterwards. For example on Linux, with the web server running as user `apache` and group `apache`, enter:
     191{{{
     192# chown -R apache.apache /path/to/myproject
     193}}}
    144194
    145195== Running the Standalone Server ==
     
    150200}}}
    151201
    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:
     202Then, 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:
    153203{{{
    154204$ tracd -s --port 8000 /path/to/myproject
    155205}}}
    156206
    157 
    158207== Running Trac on a Web Server ==
    159208
    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.
     209Trac provides various options for connecting to a "real" web server: [wiki:TracCgi CGI], [wiki:TracFastCgi FastCGI], [wiki:TracModWSGI mod_wsgi] and [wiki:TracModPython mod_python]. For decent performance, it is recommended that you use either FastCGI or mod_wsgi.
    163210
    164211Trac also supports [trac:TracOnWindowsIisAjp AJP] which may be your choice if you want to connect to IIS.
    165212
     213==== Generating the Trac cgi-bin directory ====
     214
     215In order for Trac to function properly with FastCGI you need to have a `trac.fcgi` file and for mod_wsgi a `trac.wsgi` file. These are Python scripts which load the appropriate Python code. They can be generated using the `deploy` option of [wiki:TracAdmin trac-admin].
     216
     217There 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:
     218{{{
     219mkdir -p /usr/share/trac/projects/my-project
     220trac-admin /usr/share/trac/projects/my-project initenv
     221trac-admin /usr/share/trac/projects/my-project deploy /tmp/deploy
     222mv /tmp/deploy/* /usr/share/trac
     223}}}
     224
    166225==== Setting up the Plugin Cache ====
    167226
    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.
     227Some 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 on how to set environment variables.
    169228
    170229== Configuring Authentication ==
     
    173232
    174233 * 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.
     234 * TracCgi if you use the CGI or FastCGI web front ends.
     235 * [wiki:TracModWSGI] if you use the Apache mod_wsgi web front end.
     236 * TracModPython if you use the Apache mod_python web front end.
     237
    177238
    178239== Automatic reference to the SVN changesets in Trac tickets ==
    179240
    180 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:
    181  * '''Refs #123''' - to reference this changeset in #123 ticket
    182  * '''Fixes #123''' - to reference this changeset and close #123 ticket with the default status ''fixed''
    183 
    184 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.
    185 
    186 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:
    187 
    188 {{{
    189 $ cd /path/to/svn/repository/hooks
    190 $ mv post-commit.tmpl post-commit
    191 $ chmod 755 post-commit
    192 }}}
    193 
    194 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:
    195 
    196 {{{
    197 REPOS="$1"
    198 REV="$2"
    199 TRAC_ENV="/path/to/your/trac/project"
    200 
    201 /usr/bin/python /usr/local/bin/trac-post-commit-hook -p "$TRAC_ENV" -r "$REV"
    202 }}}
    203 
    204 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].
    205 
    206 
    207 == Platform-specifics installations ==
    208 
    209  * See [trac:TracInstallPlatforms TracInstallPlatforms]
    210  
     241You can configure SVN to automatically add a reference to the changeset into the ticket comments, whenever changes are committed to the repository. The description of the commit needs to contain one of the following formulas:
     242 * '''`Refs #123`''' - to reference this changeset in `#123` ticket
     243 * '''`Fixes #123`''' - to reference this changeset and close `#123` ticket with the default status ''fixed''
     244
     245This functionality requires a post-commit hook to be installed as described in [wiki:TracRepositoryAdmin#ExplicitSync TracRepositoryAdmin], and enabling the optional commit updater components by adding the following line to the `[components]` section of your [wiki:TracIni#components-section trac.ini], or enabling the components in the "Plugins" admin panel.
     246{{{
     247tracopt.ticket.commit_updater.* = enabled
     248}}}
     249For more information, see the documentation of the `CommitTicketUpdater` component in the "Plugins" admin panel.
    211250
    212251== Using Trac ==
    213252
    214 Once you have your Trac site up and running, you should be able to browse your subversion repository, create tickets, view the timeline, etc.
     253Once you have your Trac site up and running, you should be able to create tickets, view the timeline, browse your version control repository if configured, etc.
    215254
    216255Keep 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.
     
    221260
    222261----
    223 See also:  TracInstallPlatforms, TracGuide, TracCgi, TracFastCgi, TracModPython, [wiki:TracModWSGI], TracUpgrade, TracPermissions
     262See also: [trac:TracInstallPlatforms TracInstallPlatforms], TracGuide, TracCgi, TracFastCgi, TracModPython, [wiki:TracModWSGI], TracUpgrade, TracPermissions

Search

Context Navigation

ZOO Sponsors

http://www.zoo-project.org/trac/chrome/site/img/geolabs-logo.pnghttp://www.zoo-project.org/trac/chrome/site/img/neogeo-logo.png http://www.zoo-project.org/trac/chrome/site/img/apptech-logo.png http://www.zoo-project.org/trac/chrome/site/img/3liz-logo.png http://www.zoo-project.org/trac/chrome/site/img/gateway-logo.png

Become a sponsor !

Knowledge partners

http://www.zoo-project.org/trac/chrome/site/img/ocu-logo.png http://www.zoo-project.org/trac/chrome/site/img/gucas-logo.png http://www.zoo-project.org/trac/chrome/site/img/polimi-logo.png http://www.zoo-project.org/trac/chrome/site/img/fem-logo.png http://www.zoo-project.org/trac/chrome/site/img/supsi-logo.png http://www.zoo-project.org/trac/chrome/site/img/cumtb-logo.png

Become a knowledge partner

Related links

http://zoo-project.org/img/ogclogo.png http://zoo-project.org/img/osgeologo.png