It looks like something important is not showing in the best practise
website, special variable $PATH_TO_IMAGES as per the linked example:
.. image:: $PATH_TO_IMAGES/slop-glyph.png
Let me look into this,
On Wed, Aug 9, 2017 at 2:52 PM, Peter Briggs
I've been updating the <help> section for a locally developed tool and want
to include some images, but I've had some issues trying to see them when
I've followed the instructions outlined here:
(i.e. put the images files into a 'static/images/' subdir of the tool
directory and reference them using ".. image:: picture.png")
However when I load the tool into a Galaxy using "planemo serve ..." the
images fail to render: I just get a line of text with the image filename.
The same thing happens when I add the tool manually on our local server
(i.e. by adding a <tool file=...> reference to the tool XML in the
appropriate conf.xml file).
If I upload the same tool files to a toolshed and then install from there, I
do see the images rendered correctly.
I'm a bit baffled as to why there should be a difference. Is there an option
or setting I've missed to turn on the image rendering for non-shed-installed
tools? Or have I made some other mistake?
Thanks for your help,
Peter Briggs peter.briggs(a)manchester.ac.uk
Bioinformatics Core Facility University of Manchester
B.1083 Michael Smith Bldg Tel: (0161) 2751482
Please keep all replies on the list by using "reply all"
in your mail client. To manage your subscriptions to this
and other Galaxy lists, please use the interface at:
To search Galaxy mailing lists use the unified search at: