Ticket #9462 (closed enhancement: fixed)
Opened 20 months ago
Last modified 16 months ago
[PATCH] Add shared htdocs location
| Reported by: | itamaro | Owned by: | itamaro |
|---|---|---|---|
| Priority: | normal | Milestone: | 0.13 |
| Component: | general | Version: | 0.12 |
| Severity: | normal | Keywords: | chrome site inherit htdocs needfixup |
| Cc: | osimons | ||
| Release Notes: |
web: [inherit] htdocs_dir setting can be used to specify a shared location for resources, reachable using the "/htdocs/shared/" prefix. |
||
| API 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.
Attachments
Change History
Changed 20 months ago by itamaro
- Attachment shared_htdocs.patch added
comment:1 Changed 17 months ago by cboos
Can you explain a bit more what would be the use case for this?
comment:2 Changed 17 months ago by itamaro
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
comment:3 follow-up: ↓ 8 Changed 17 months ago by cboos
- Keywords site inherit htdocs needfixup added
- Milestone set to 0.13
- Owner set to itamaro
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.
comment:4 follow-up: ↓ 5 Changed 17 months ago by rblank
IIRC, we removed a stock site.html quite recently (#8869), to avoid its hiding a shared site.html.
comment:5 in reply to: ↑ 4 ; follow-up: ↓ 6 Changed 17 months ago by cboos
Replying to rblank:
IIRC, we removed a stock site.html quite recently (#8869), to avoid its hiding a shared site.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 in reply to: ↑ 5 Changed 17 months ago by rblank
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 Changed 17 months ago by osimons
- Cc osimons added
comment:8 in reply to: ↑ 3 Changed 17 months ago by itamaro
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 Changed 16 months ago by cboos
- Release Notes modified (diff)
- Resolution set to fixed
- Status changed from new to closed



Add shared htdocs_dir directory and return it from Chrome.get_htdocs_dirs()