#1825 closed defect (fixed)
[patch] TRAC_ENV_PARENT_DIR support for tracd
Reported by: | Christian Boos | Owned by: | Matthew Good |
---|---|---|---|
Priority: | normal | Milestone: | 0.9 |
Component: | web frontend/tracd | Version: | devel |
Severity: | normal | Keywords: | |
Cc: | Branch: | ||
Release Notes: | |||
API Changes: | |||
Internal Changes: |
Description
I'd like to follow-up on r2015 by adding tracd support, but as I don't use the other front-ends (*cgi and mod_python), I don't know if this would break something.
Here's an early patch, which seems to work. I'll refine it further tomorrow, but if in the meantime someone could test it against the other front-ends, I would be interested to know if I broke something.
Thanks
Attachments (1)
Change History (4)
by , 19 years ago
Attachment: | 2015_tracd.diff added |
---|
comment:1 by , 19 years ago
Owner: | changed from | to
---|---|
Status: | new → assigned |
Well, for tracd using an environment variable would be inconsistent with it's normal usage. Using another command-line argument would be more appropriate. I'll go ahead and look into that.
comment:2 by , 19 years ago
Using another command-line argument would be more appropriate.
No problem. The point was not really to support the TRAC_ENV_PARENT_DIR
environment variable as such, but the concept behind, i.e. having Trac
automatically serve a set of environments collocated in the same directory.
A corrollary for that feature would be:
- the ability to share a common configuration file which could be used to set up common defaults for those environments. How is #1051 going in that respect?
- the ability to share a common authorization file between those environments.
comment:3 by , 19 years ago
Resolution: | → fixed |
---|---|
Status: | assigned → closed |
Ok, [2035] added the command line option "-e" or "—env-parent-dir" to specify the parent directory to serve projects from.
initial patch