Changes between Version 3 and Version 4 of TracEnvironment


Ignore:
Timestamp:
May 6, 2010, 11:40:32 PM (14 years ago)
Author:
trac
Comment:

--

Legend:

Unmodified
Added
Removed
Modified

  • TracEnvironment

    v3 v4  
    1010}}}
    1111
    12 [wiki:TracAdmin trac-admin] will ask you for the name of the project, the
    13 database connection string (explained below), and the type and path to
    14 your source code repository.
     12[wiki:TracAdmin trac-admin] will ask you for the name of the project and the
     13database connection string (explained below).
    1514
    16 ''Note: The web server user will require file system write permission to
     15''Note: The user under which the web server runs will require file system write permission to
    1716the environment directory and all the files inside. Please remember to set
    18 the appropriate permissions. The same applies to the Subversion repository
    19 Trac is eventually using, although Trac will only require read access as long
    20 as you're not using the BDB file system. Also, it seems that project names
    21 with spaces can be problematic for authentication (see [trac:#7163]).''
     17the appropriate permissions. The same applies to the source code repository,
     18although the user under which Trac runs will only require write access to a Subversion repository created with the BDB file system
     19; for other repository types, check the corresponding plugin's documentation.
     20Also, it seems that project names with spaces can be problematic for authentication (see [trac:#7163]).''
    2221
    2322''Note: "initenv" when using svn repository does not imply that trac-admin will perform "svnadmin create" for the specified repository path. You need to perform the "svnadmin create" prior to trac-admin initenv if you're creating a new svn repository altogether with a new trac environment, otherwise you will see a message "Warning: couldn't index the repository" when initializing the environment.''
    … …  
    3231[wiki:TracBackup backed up] together with the rest of the environment.
    3332
    34 === Embedded SQLite Connection String ===
    35 The connection string for an embedded SQLite database is:
     33=== SQLite Connection String ===
     34The connection string for an SQLite database is:
    3635{{{
    3736sqlite:db/trac.db
    3837}}}
     38where `db/trac.db` is the path to the database file within the Trac environment.
    3939
    4040=== PostgreSQL Connection String ===
    … …  
    9797== Source Code Repository ==
    9898
    99 You'll first have to provide the ''type'' of your repository (e.g. `svn` for Subversion,
    100 which is the default), then the ''path'' where the repository is located.
     99Since version 0.12, a single Trac environment can be connected to more than one repository. There are many different ways to connect repositories to an environment, see TracRepositoryAdmin. This page also details the various attributes that can be set for a repository (like `type`, `url`, `description`).
    101100
    102 If you don't want to use Trac with a source code repository, simply leave the ''path'' empty
    103 (the ''type'' information doesn't matter, then).
     101In Trac 0.12 `trac-admin` no longer asks questions related to repositories. Therefore, by default Trac is not connected to any source code repository, and the ''Browse Source'' toolbar item will not be displayed.
     102You can also explicitly disable the `trac.versioncontrol.*` components (which are otherwise still loaded)
     103{{{
     104[components]
     105trac.versioncontrol.* = disabled
     106}}}
    104107
    105 For some systems, it is possible to specify not only the path to the repository,
     108For some version control systems, it is possible to specify not only the path to the repository,
    106109but also a ''scope'' within the repository. Trac will then only show information
    107110related to the files and changesets below that scope. The Subversion backend for
    108111Trac supports this; for other types, check the corresponding plugin's documentation.
    109112
    110 Example of a configuration for a Subversion repository:
     113Example of a configuration for a Subversion repository used as the default repository:
    111114{{{
    112115[trac]
    … …  
    135138 * `htdocs` - directory containing web resources, which can be referenced in Genshi templates. '''''(since 0.11)'''''
    136139 * `log` - default directory for log files, if logging is turned on and a relative path is given.
    137  * `plugins` - Environment-specific [wiki:TracPlugins plugins] (Python eggs, since [trac:milestone:0.10 0.10])
     140 * `plugins` - Environment-specific [wiki:TracPlugins plugins] (Python eggs or single file plugins, since [trac:milestone:0.10 0.10])
    138141 * `templates` - Custom Genshi environment-specific templates. '''''(since 0.11)'''''
    139142   * `site.html` - method to customize header, footer, and style, described in TracInterfaceCustomization#SiteAppearance
    140143
    141   '''Note: don't confuse a Trac environment directory with the source code repository directory.
    142 It happens that the above structure is loosely modelled after the Subversion repository directory
    143 structure, but they are not and ''must not'' be located at the same place.'''
     144'''Caveat:''' ''don't confuse a Trac environment directory with the source code repository directory.''
     145
     146This is a common beginners' mistake.
     147It happens that the structure for a Trac environment is loosely modelled after the Subversion repository directory
     148structure, but those are two disjoint entities and they are not and ''must not'' be located at the same place.
    144149
    145150----