Changes between Version 53 and Version 54 of TracMultipleProjects

Timestamp:

Jun 17, 2005, 1:32:20 PM (19 years ago)

Author:

mechanix

Comment:

correct easy Apache 2 method and move to top

TracMultipleProjects

@@ -1 +1 @@
 = Configure Apache for multiple projects =
-
-By following these instructions, you will set up Apache to automatically serve multiple Trac projects for you. There are two different ways of setting this up: with and without global authentication.
-
-== URL Rewriting ==
-
-
-Both ways use Apache's URL rewriting module : {{{mod_rewrite}}}. You have to make sure you have it loaded or compiled in Apache.
+By following these instructions, you will set up Apache to automatically serve multiple Trac projects for you. There are two different ways of setting this up: with and without global authentication. And with Apache 2 there are even two ways to do both.
+
+== Easiest method for hosting multiple projects in one domain with Apache 2 ==
+The first way to support multiple projects is to add the following to the Apache 2 config file, per project (myproj in this case):
+
+{{{
+ScriptAlias /myproj /path/to/trac.cgi
+
+<Location "/myproj">
+    SetEnv TRAC_ENV "/var/trac/myproj"
+</Location>
+
+<Location "/myproj/login">
+    AuthType basic
+    AuthName "myproj - trac"
+    AuthUserFile "/var/svn/svn-auth-file"
+    Require valid-user
+</Location>
+}}}
+
+This is in addition to the global line:
+
+{{{
+Alias /trac "/usr/share/trac/htdocs"
+}}}
+
+If you want different users per project, just edit the !AuthUserFile line for each one.
+
+== Harder method: URL Rewriting ==
+In this case both ways use Apache's URL rewriting module : {{{mod_rewrite}}}. You have to make sure you have it loaded or compiled in Apache.
 
 === Apache 1.x ===
-
 In 1.x versions of the Apache web server, you must uncomment the following line in the main Apache configuration file, generally found at {{{/etc/apache/apache.conf}}} or {{{/etc/httpd/httpd.conf}}} :
 
@@ -17 +39 @@
 
 === Apache 2.x ===
-
 Newer versions of Apache (> 2.x) uses a cleaner configuration system. In the directory {{{/etc/apache2/mods-available/}}} are all modules loading and configuration snippets available. In {{{/etc/apache2/mods-enabled/}}} are all enabled modules. You just need to check that a symlink to the rewrite module loading file is present. If not, create it :
 
@@ -31 +52 @@
 }}}
 
-== Global ==
-
+== Global authentication ==
 This is the simplest case. With this procedure, you will be able to serve multiple Trac projects, using the same user accounts for every projects (permissions are still per project, but authentication is not). This is the original procedure provided by the Trac team.
 
@@ -79 +99 @@
 '''Suggestion:''' In the second ''RewriteRule'' directive and in the ''LocationMatch'' directive, change {{{[[:alnum:]]}}} to {{{[^/]}}} because while {{{[[:alnum:]]}}} only matches an alpha-numeric character, {{{[^/]}}} matches any character that is not a slash.  This change allows for, among other things, hyphens in project/directory names.  Another possibility is to replace {{{[[:alnum:]]}}} with {{{[[:alnum:]\-]}}}, which matches only an alphanumeric character or a hyphen (the backslash "escapes" the hyphen, which would otherwise have special meaning).  The [http://httpd.apache.org/docs-2.0/mod/mod_rewrite.html Apache 2.0 mod_rewrite documentation] suggests referencing the Perl regular expression manual page (run {{{perldoc perlre}}} on a system where Perl is installed) for details on regular expressions.  Note that it may be preferable to use a pattern that matches only characters suitable for directory names (and, thus, project names) that are valid for your particular installation.
 
-== Per-project ==
-
+== Per-project authentication ==
 As you problably noticed, the global procedure described above uses the same {{{AuthUserFile}}}, so every user you create in this file can log in every Trac project you host. Of course, in a non-configured Trac env, this user will be considered as ''anonymous'', but you might not want this too. Using a per-project authentification also allows you to use a different authentification greater for each project.
 
@@ -86 +105 @@
 
 === Preparation ===
-
 As for the first procedure, you'll need a {{{projects}}} directory into your !DocumentRoot. Copy or symlink {{{trac.cgi}}} to this project :
 
@@ -97 +115 @@
 
 === Apache configuration ===
-
 The begining is exactly the same than for the global authentification installation :
 
@@ -155 +172 @@
 
 === Auth files and project listing ===
-
 In order to complete this setup, you will need two authentification files :
 
@@ -211 +227 @@
 Here you are ! Don't forget to ''chown'' these files to {{{www-data}}}, and it should work !
 
-=== Alternative method for hosting multiple projects in one domain ===
-
-Another way to support multiple projects is to add the following to the Apache 2 config file, per project (myproj in this case):
-
-{{{
-ScriptAlias /myproj /
-
-<Location "/myproj">
-        SetEnv TRAC_ENV "/var/trac/myproj"
-</Location>
-
-<Location "/myproj/login">
-          AuthType basic
-          AuthName "trac"
-          AuthUserFile "/var/svn/svn-auth-file"
-          Require valid-user
-</Location>
-}}}
-
-This is in addition to the global line:
-
-{{{
-Alias /trac "/usr/share/trac/htdocs"
-}}}
-
-If you want different users per project, just edit the !AuthUserFile line for each one.
-
 -------
 See also: TracGuide, TracInstall, TracMultipleProjectsWindows