Changes between Version 1 and Version 2 of TracModPython

Timestamp:

Dec 7, 2010, 10:14:17 PM (14 years ago)

Author:

trac

Comment:

--

TracModPython

@@ -13 +13 @@
 }}}
 
- ''Note: The exact path to the module depends on how the HTTPD installation is laid out.''
+''Note: The exact path to the module depends on how the HTTPD installation is laid out.''
+
 On Debian using apt-get
 {{{
@@ -57 +58 @@
     PythonOption TracEnvParentDir /var/trac/myprojects
     # For the index of multiple projects
-    PythonOption TracEnvIndexTemplate /srv/www/htdocs/trac/project_list_tepmlate.html
+    PythonOption TracEnvIndexTemplate /srv/www/htdocs/trac/project_list_template.html
     # A space delimitted list, with a "," between key and value pairs.
     PythonOption TracTemplateVars key1,val1 key2,val2
@@ -64 +65 @@
     # See description above        
     PythonOption TracUriRoot /projects/myproject
+}}}
+
+=== Python Egg Cache ===
+
+Compressed python eggs like Genshi are normally extracted into a directory named `.python-eggs` in the users home directory. Since apache's home usually is not writable an alternate egg cache directory can be specified like this:
+{{{
+PythonOption PYTHON_EGG_CACHE /var/trac/myprojects/egg-cache
 }}}
 
@@ -217 +225 @@
 }}}
 
-if you have issues with login try using `<LocationMatch>` instead of `<Location>`
+This does not seem to work in all cases. What you can do if it does not:
+ * Try using `<LocationMatch>` instead of `<Location>`
+ * <Location /> may, in your server setup, refer to the complete host instead of simple the root of the server. This means that everything (including the login directory referenced below) will be sent to python and authentication does not work (i.e. you get the infamous Authentication information missing error). If this applies to you, try using a sub-directory for trac instead of the root (i.e. /web/ and /web/login instead of / and /login).
 
 For a virtual host that supports multiple projects replace "`TracEnv`" /var/trac/myproject with "`TracEnvParentDir`" /var/trac/
 
-Note: !DocumentRoot should not point to your Trac project env. As Asmodai wrote on #trac: "suppose there's a webserer bug that allows disclosure of !DocumentRoot they could then leech the entire Trac environment".
+Note: !DocumentRoot should not point to your Trac project env. As Asmodai wrote on #trac: "suppose there's a webserver bug that allows disclosure of !DocumentRoot they could then leech the entire Trac environment".
 
 == Troubleshooting ==
@@ -261 +271 @@
 
 It may be possible to work around this with mod_rewrite, but I failed to get this working. In all, it is more hassle than it is worth. Stick to the provided instructions. :)
+
+A success story: For me it worked out-of-box, with following trivial config:
+{{{
+SetHandler mod_python
+PythonInterpreter main_interpreter
+PythonHandler trac.web.modpython_frontend 
+PythonOption TracEnv /system/path/to/this/directory
+PythonOption TracUriRoot /path/on/apache
+
+AuthType Basic
+AuthName "ProjectName"
+AuthUserFile /path/to/.htpasswd
+Require valid-user
+}}}
+
+The TracUriRoot is obviously the path you need to enter to the browser to get to the trac (e.g. domain.tld/projects/trac)
+
+=== Additional .htaccess help ===
+
+If you are using the .htaccess method you may have additional problems if your trac directory is inheriting .htaccess directives from another.  This may also help to add to your .htaccess file:
+
+{{{
+<IfModule mod_rewrite.c>
+  RewriteEngine Off
+</IfModule>
+}}}
+
 
 === Win32 Issues ===
@@ -339 +376 @@
 
 ----
-See also TracGuide, TracInstall, TracCgi, TracFastCgi
+See also:  TracGuide, TracInstall, [wiki:TracModWSGI ModWSGI], [wiki:TracFastCgi FastCGI], [wiki:TracModPython ModPython], [trac:TracNginxRecipe TracNginxRecipe]