Changes between Version 4 and Version 5 of TracEnvironment

Timestamp:

Apr 13, 2010, 3:53:03 AM (14 years ago)

Author:

trac

Comment:

--

TracEnvironment

@@ -10 +10 @@
 }}}
 
-[wiki:TracAdmin trac-admin] will ask you for the name of the project and the
-database connection string (explained below).
+[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.
 
-''Note: The user under which the web server runs will require file system write permission to 
+''Note: The web server user will require file system write permission to 
 the environment directory and all the files inside. Please remember to set
-the appropriate permissions. The same applies to the source code repository, 
-although the user under which Trac runs will only require write access to a Subversion repository created with the BDB file system
-; for other repository types, check the corresponding plugin's documentation. 
-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.''
+the appropriate permissions. The same applies to the Subversion repository 
+Trac is eventually using, although Trac will only require read access as long 
+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]).''
 
 == Database Connection Strings ==
@@ -31 +30 @@
 [wiki:TracBackup backed up] together with the rest of the environment.
 
-=== SQLite Connection String ===
-The connection string for an SQLite database is:
+=== Embedded SQLite Connection String ===
+The connection string for an embedded SQLite database is:
 {{{
 sqlite:db/trac.db
 }}}
-where `db/trac.db` is the path to the database file within the Trac environment.
 
 === PostgreSQL Connection String ===
@@ -97 +95 @@
 == Source Code Repository ==
 
-Since 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`).
+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.
 
-In 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.
-You can also explicitly disable the `trac.versioncontrol.*` components (which are otherwise still loaded)
-{{{
-[components]
-trac.versioncontrol.* = disabled
-}}}
+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).
 
-For some version control systems, it is possible to specify not only the path to the repository,
+For some systems, it is possible to specify not only the path to the repository,
 but also a ''scope'' within the repository. Trac will then only show information
 related to the files and changesets below that scope. The Subversion backend for
 Trac supports this; for other types, check the corresponding plugin's documentation.
 
-Example of a configuration for a Subversion repository used as the default repository:
+Example of a configuration for a Subversion repository:
 {{{
 [trac]
@@ -136 +131 @@
  * `db`
    * `trac.db` - The SQLite database (if you're using SQLite).
- * `htdocs` - directory containing web resources, which can be referenced in Genshi templates. '''''(since 0.11)'''''
+ * `htdocs` - directory containing web resources, which can be referenced in Genshi templates. '''''(0.11 only)'''''
  * `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 or single file plugins, since [trac:milestone:0.10 0.10])
- * `templates` - Custom Genshi environment-specific templates. '''''(since 0.11)'''''
+ * `plugins` - Environment-specific [wiki:TracPlugins plugins] (Python eggs, since [trac:milestone:0.10 0.10])
+ * `templates` - Custom Genshi environment-specific templates. '''''(0.11 only)'''''
    * `site.html` - method to customize header, footer, and style, described in TracInterfaceCustomization#SiteAppearance
+ * ''`templates` - Custom [trac:ClearSilver 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.''
+ * ''`wiki-macros` - Environment-specific [WikiMacros Wiki macros]. '''(0.10 only)''' ''
 
-'''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.
+  '''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.'''
 
 ----
 See also: TracAdmin, TracBackup, TracIni, TracGuide
-