The tool_config_file setting in universe_wsgi.ini must include at least one shed tool configuration file name with a <toolbox> tag that includes a tool_path attribute value which is a directory relative to the Galaxy installation directory in order to automatically install tools from a Galaxy tool shed (e.g., the file name shed_tool_conf.xml whose <toolbox> tag is <toolbox tool_path="../shed_tools">).

See the Automatic installation of Galaxy tool shed repository tools into a local Galaxy instance section of the Galaxy tool shed wiki for all of the details.

Any help interpreting this would be greatly appreciated!

Cheers,

Mo Heydarian

On Tue, Jul 31, 2012 at 4:11 PM, Dannon Baker <dannonbaker@me.com> wrote:

The problem here is that the public toolshed interface has been updated more recently than the galaxy install on that cloud instance. You should be good to go if you update galaxy (possible through the admin interface at <your_ec2_instance>/cloud/admin/) to the latest version.

-Dannon

On Jul 31, 2012, at 12:11 PM, Mohammad Heydarian <mheydarian@gmail.com> wrote:

> Hi Galaxy Community!
> Hope all is well.
>
> I've been trying to install some tools in my Galaxy Cloudman instance (using image: ami-da58aab3 ) from the main toolshed. When I try to "install to local Galaxy" I get the error:
>
> Not Found
>
> The resource could not be found.
> No action for /admin_toolshed/prepare_for_install
>
>
>
> I have tried to load tools on a couple of different Cloudman instances and tried to load a variety of tools and end up with the same error. Any help would be fantastic.
>
> Cheers,
> Mo Heydarian
>
>
>

> ___________________________________________________________
> 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:
>
> http://lists.bx.psu.edu/