Trac integration instructions bad

[GoogleCodeExporter]

The bottom section of the Trac guide (the part about multiple environments) is 
very over-
engineered. All that is needed is to set trac.env_parent_dir, it will do the 
indexing and such 
automatically.

Original issue reported on code.google.com by coderan...@gmail.com on 26 Oct 2007 at 1:18

[GoogleCodeExporter]

I had some reason for doing it the way I did originally, but can't remember 
right
now. It may have been in part that this example was contracted from a more 
complex
example I was playing with where rewrite maps were used to map some varying URL 
to
varying file system path, thereby providing a possibly more flexible mapping 
above
what Trac may have been able to do with parent directory option. Ie., the URL 
name
wouldn't have to match Trac directory name on disk. Thus could spread Trac 
instances
out across different users accounts. I'll revisit this and try and work out 
what I
was thinking of. :-)

Original comment by Graham.Dumpleton@gmail.com on 26 Oct 2007 at 1:44

• Added labels: Type-Task
• Removed labels: Type-Defect

[GoogleCodeExporter]

Document did refer to TRAC_ENV_PARENT_DIR mechanism for hosting multiple sites 
and
referred to WSGI equivalent in translation table to variable names. Document did
assume though that user new what TRAC_ENV_PARENT_DIR was all about in the first
place. The rewrite rule approach was shown as an equivalent to 
TRAC_ENV_PARENT_DIR as
a basis for people wanted to create a more flexible system where there wasn't
necessarily a direct mapping of URL component to a Trac instance directory.

Anyway, have expanded on what TRAC_ENV_PARENT_DIR is all about and clarified the
intent of some of the more complex examples.

Original comment by Graham.Dumpleton@gmail.com on 26 Oct 2007 at 5:20

• Changed state: Fixed