Opened 14 years ago
Closed 14 years ago
#9462 closed enhancement (fixed)
[PATCH] Add shared htdocs location — at Version 9
| Reported by: | Itamar Ostricher | Owned by: | Itamar Ostricher |
|---|---|---|---|
| Priority: | normal | Milestone: | 1.0 |
| Component: | general | Version: | 0.12 |
| Severity: | normal | Keywords: | chrome site inherit htdocs needfixup |
| Cc: | osimons | Branch: | |
| Release Notes: |
web: |
||
| API Changes: | |||
| Internal Changes: | |||
Description
Allow multiple Trac environments to share the same htdocs directory, similar to the concept of a shared templates directory.
Attached patch (against 0.12 tag) adds htdocs_dir to [inherit] option group, and maps this directory to chrome/shared URL in Chrome.get_htdocs_dirs() under the 'shared' prefix.
Change History (10)
by , 14 years ago
| Attachment: | shared_htdocs.patch added |
|---|
comment:2 by , 14 years ago
of course.
This patch is a result of the following discussion on the mailing list: http://groups.google.com/group/trac-users/browse_thread/thread/ad54345c3fddd3be/b79c4ca9b4d56fab
follow-up: 8 comment:3 by , 14 years ago
| Keywords: | site inherit htdocs needfixup added |
|---|---|
| Milestone: | → 0.13 |
| Owner: | set to |
Ok, I see, thanks for the reference.
Can you update the option documentation by also saying "This can be useful in site.html" (as well as the "since").
Which makes me think about creating a default site.html (with the same content as in TracInterfaceCustomization#SiteAppearance) on initenv, as well as a default site.css (empty, or even with something distinctively not "edgewall" like, to help for #6185). That would make customization of new environments a tad easier.
follow-up: 5 comment:4 by , 14 years ago
IIRC, we removed a stock site.html quite recently (#8869), to avoid its hiding a shared site.html.
follow-up: 6 comment:5 by , 14 years ago
Replying to rblank:
IIRC, we removed a stock
site.htmlquite recently (#8869), to avoid its hiding a sharedsite.html.
Ah yes, [8952] which produces a site.html.sample.
Still, there are too many steps to perform in order to do some simple CSS customizations (like, adding a color for a group in [milestone-groups] ). Perhaps we could always provide a link to the site.css files present in any of the get_htdocs_dirs()?
comment:6 by , 14 years ago
Replying to cboos:
Perhaps we could always provide a link to the site.css files present in any of the
get_htdocs_dirs()?
Yes, I was thinking the same.
comment:7 by , 14 years ago
| Cc: | added |
|---|
comment:8 by , 14 years ago
Replying to cboos:
Can you update the option documentation by also saying "This can be useful in site.html" (as well as the "since").
Updated (see the branch on my fork at GitHub: http://github.com/itamaro/trac/tree/9462-shared-htdocs).
comment:9 by , 14 years ago
| Release Notes: | modified (diff) |
|---|---|
| Resolution: | → fixed |
| Status: | new → closed |
Add shared htdocs_dir directory and return it from Chrome.get_htdocs_dirs()