Changes between Version 1 and Version 2 of TracEnvironment

Timestamp:

Feb 24, 2010 5:37:18 PM (11 years ago)

Author:

trac

Comment:

--

TracEnvironment

@@ -10 +10 @@
 }}}
 
-[wiki:TracAdmin trac-admin] will ask you for the name of the project, the
-database connection string (explained below), and the type and path to
-your source code repository.
+[wiki:TracAdmin trac-admin] will ask you for the name of the project and the
+database connection string (explained below).
 
 ''Note: The web server user will require file system write permission to 
@@ -20 +19 @@
 as you're not using the BDB file system. Also, it seems that project names
 with spaces can be problematic for authentication (see [trac:#7163]).''
+
+''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.''
 
 == Database Connection Strings ==
@@ -95 +96 @@
 == Source Code Repository ==
 
-You'll first have to provide the ''type'' of your repository (e.g. `svn` for Subversion,
-which is the default), then the ''path'' where the repository is located.
+Since version 0.12, one Trac environment can be tied to more than one repository. There are many different ways to add repositories to an environment, see TracRepositoryAdmin. This page also details the various attributes that can be set on a repository (like `type`, `url`, `description`).
 
-If you don't want to use Trac with a source code repository, simply leave the ''path'' empty
-(the ''type'' information doesn't matter, then).
+If you don't want to use Trac with any source code repository, at creation time simply leave the ''path'' empty
+(the ''type'' information doesn't matter in this case). Then you also need to disable the `trac.versioncontrol.*` components:
+{{{
+[components]
+trac.versioncontrol.* = disabled
+}}}
 
 For some systems, it is possible to specify not only the path to the repository,
@@ -106 +110 @@
 Trac supports this; for other types, check the corresponding plugin's documentation.
 
-Example of a configuration for a Subversion repository:
+Example of a configuration for a Subversion repository used as the default repository:
 {{{
 [trac]
@@ -131 +135 @@
  * `db`
    * `trac.db` - The SQLite database (if you're using SQLite).
- * `htdocs` - directory containing web resources, which can be referenced in Genshi templates. '''''(0.11 only)'''''
+ * `htdocs` - directory containing web resources, which can be referenced in Genshi templates. '''''(since 0.11)'''''
  * `log` - default directory for log files, if logging is turned on and a relative path is given.
- * `plugins` - Environment-specific [wiki:TracPlugins plugins] (Python eggs, since [milestone:0.10])
- * `templates` - Custom ClearSilver environment-specific templates. '''''(0.10 only)'''''
-   * `site_css.cs` - Custom CSS rules.
-   * `site_footer.cs` - Custom page footer.
-   * `site_header.cs` - Custom page header.
- * `templates` - Custom Genshi environment-specific templates. '''''(0.11 only)'''''
+ * `plugins` - Environment-specific [wiki:TracPlugins plugins] (Python eggs or single file plugins, since [trac:milestone:0.10 0.10])
+ * `templates` - Custom Genshi environment-specific templates. '''''(since 0.11)'''''
    * `site.html` - method to customize header, footer, and style, described in TracInterfaceCustomization#SiteAppearance
- * `wiki-macros` - Environment-specific [WikiMacros Wiki macros]. '''''(0.10 only)'''''
 
-  '''Note: don't confuse a Trac environment directory with the source code repository directory.
-It happens that the above structure is loosely modelled after the Subversion repository directory 
-structure, but they are not and ''must not'' be located at the same place.'''
+'''Caveat:''' ''don't confuse a Trac environment directory with the source code repository directory.''
+
+This is a common beginners' mistake.
+It happens that the structure for a Trac environment is loosely modelled after the Subversion repository directory 
+structure, but those are two disjoint entities and they are not and ''must not'' be located at the same place.
 
 ----
 See also: TracAdmin, TracBackup, TracIni, TracGuide
+