[tahoe-lafs-trac-stream] [tahoe-lafs] #1828: Problem with linked images' display in rst docs from trac

[tahoe-lafs]

#1828: Problem with linked images' display in rst docs from trac
-------------------------+--------------------------
     Reporter:  mk.fg    |      Owner:  zooko
         Type:  defect   |     Status:  assigned
     Priority:  minor    |  Milestone:  undecided
    Component:  website  |    Version:  n/a
   Resolution:           |   Keywords:  website docs
Launchpad Bug:           |
-------------------------+--------------------------

Comment (by mk.fg):

 Apologies for snippet being unhelpful, should've explained it with words.

 The above tweak doesn't make nginx serve files as such, they are still
 served by trac, just as per the following link:

   https://tahoe-lafs.org/trac/tahoe-
 lafs/export/master/git/docs/specifications/file-encoding1.svg

 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.

 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.

 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.

 Does it make any sense?

-- 
Ticket URL: <https://tahoe-lafs.org/trac/tahoe-lafs/ticket/1828#comment:6>
tahoe-lafs <https://tahoe-lafs.org>
secure decentralized storage