Changes between Initial Version and Version 1 of Ticket #1828, comment 6
- Timestamp:
- 2012-10-25T18:56:35Z (13 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
TabularUnified Ticket #1828, comment 6
initial v1 5 5 https://tahoe-lafs.org/trac/tahoe-lafs/export/master/git/docs/specifications/file-encoding1.svg 6 6 7 What it does is for any uri like " browser/git/docs/specifications/file-encoding1.svg" (common prefix omitted, matching regexp pattern in the location block) to pass uri like "export/master/git/docs/specifications/file-encoding1.svg" to uwsgi and trac, so it will serve the raw file back to nginx.7 What it does is for any uri like "/trac/tahoe-lafs/browser/git/docs/specifications/file-encoding1.svg" (matching regexp pattern in the location block) to pass uri like "/trac/tahoe-lafs/export/master/git/docs/specifications/file-encoding1.svg" to uwsgi and trac, so it will serve the raw file back to nginx. 8 8 9 I.e. it doesn't work around trac (which might be a bad idea, and probably not so easy for a bare git repo), so all the trac checks and tricks are in place, and it will only apply to "docs/" path in git.9 I.e. it doesn't work around trac (which might be a bad idea, and probably not so easy to do for a bare git repo), so all the trac checks and tricks are in place, and it will only apply to "docs/" path in git. 10 10 11 I'm afraid I'm not aware of a way to make trac serve raw images by default and looking over git configuration section in a trac I maintain, I can't see any option to make it do that (as I ''think'' it did with darcs), but if such option exists, imho it might a bit more consistent solution, though maybe a bit less convenient since it might be undesirable to display raw image attachments in wiki and tickets.11 I'm afraid I'm not aware of a way to make trac serve raw images by default and looking over git configuration section in a trac I maintain, I can't see any option to make it do that (as I ''think'' it did with darcs), but if such option exists, imho it might be a bit more consistent solution, though maybe a bit less convenient since it might be undesirable to display raw image attachments in wiki and tickets. 12 12 13 13 Does it make any sense?
