I am skeptical that setting up a local tool shed is worth the effort -
it seems like overkill. I think just downloading the tar balls,
manually modifying the datatypes_conf.xml is fine.
If you set the tool_dependencies_dir in your Galaxy configuration -
you can also create a isolated environments
I can try a local toolshed, but the organization I work at frowns upon
automatic installation for various reasons. That and it lets me see
exactly how a tool is installed and works within my local instance.
When a tool is installed from the toolshed, how does Galaxy know about it?
>From a DB entr
Hi Ryan,
what about a local bootstrapped ToolShed which is in sync with the
public one (at least for the users you are interested on). Than you can
install from this ToolShed. I guess this is less annoying than
maintaining everything on your own.
Cheers,
Bjoern
Am 16.01.2015 um 08:22 schrieb Pet
On Thu, Jan 15, 2015 at 6:57 PM, Ryan G wrote:
> Because of the way the infrastructure for my Galaxy instance is set up, I
> need to download and install tools from the toolshed manually. For most of
> the tools, this is pretty easy, however I'm now trying to add RSEM to my
> instance and it has
Because of the way the infrastructure for my Galaxy instance is set up, I
need to download and install tools from the toolshed manually. For most of
the tools, this is pretty easy, however I'm now trying to add RSEM to my
instance and it has some new datatypes.
Along with the new data types is py
