On Jun 27, 2012, at 5:59 PM, Dorset, Daniel C wrote:
> We have an instance of Galaxy deployed on a local institutional cluster. It’s
> working well, but when we import BED files for visualization, Galaxy runs the
> processing for these on the cluster. I would like to run these tasks locally
> I understand how to make individual tools run locally, but I’m hoping there’s
> a better way to accomplish what I would like to do without having to specify
> each of the many conversion tools individually in the universe_wsgi.ini
> config file.
Unfortunately, you can only do it on a per-tool basis in the
[galaxy:tool_runners] section of the config. However, you can set separate
runners for the regular invocation of the converters and ones run from
Trackster by using the syntax:
<tool id>[source@trackster] = <runner_url>
All of <tool id> (including the angle brackets) should be replaced with the
actual tool id, but [source@trackster] (including the square brackets) should
be exactly as shown.
> 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:
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: