On Fri, Aug 3, 2012 at 11:07 PM, Nikhil Joshi wrote:
> Hey Mo,
>
> So I'm figuring out the same issues, and I think I have been able to
> figure it out but for sure you need to uncomment the
> tool_config_file and tool_path lines in your universe_wsgi.ini file,
> probably should create a new d
Thanks for this.
I updated my local version of Galaxy Cloudman and tried loading a tool and
got a new error:
The *tool_config_file* setting in *universe_wsgi.ini* must include at least
one shed tool configuration file name with a ** tag that includes
a *tool_path* attribute value which is a direc
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
/cloud/admin/) to the latest version.
-Dannon
On Jul 31, 2012, at 12:11
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/pre
