Changes between Version 12 and Version 13 of 0.12/TracInstall

Timestamp:

Feb 3, 2010, 12:19:21 PM (14 years ago)

Author:

Christian Boos

Comment:

#CreatingaProjectEnvironment: rewritten parts about the repository setup (+ a link to TracRepositoryAdmin)

0.12/TracInstall

@@ -169 +169 @@
 == Creating a Project Environment ==
 
-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.
+A [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.
 
 A new environment is created using [wiki:TracAdmin trac-admin]:
@@ -176 +176 @@
 }}}
 
-[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.
-
-Also note that the values you specify here can be changed later by directly editing the [wiki:TracIni] configuration file.
-
-''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:''
-
-  chown -R apache.apache /path/to/myproject
+[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 [TracEnvironment#SourceCodeRepository source code repository] for setting up the default repository, the [TracEnvironment#DatabaseConnectionStrings database connection string], and so on. If you're not sure what to specify for one of these options, just press `<Enter>` to use the default value. 
+
+Leaving the database connection string empty in particular will always work as long as you have SQLite installed.
+For the other [DatabaseBackend database backends] you should plan ahead and already have a database ready to use at this point.
+
+Leaving the path to the source code repository empty only means that you won't have a ''default'' repository defined. You change this, add one or more ''named'' repositories by [TracRepositoryAdmin managing repositories] afterwards, or even disable the version control support completely if you don't need it.
+
+Also note that the values you specify here can be changed later by directly editing the [TracIni conf/trac.ini] configuration file.
+
+Finally, 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:
+{{{
+# chown -R apache.apache /path/to/myproject
+}}}
 
 == Running the Standalone Server ==