Toolshed initial upload errors out
As per the title, I'm trying to setup a toolshed for our local use. After creating a repo, I try to upload the initial file only to get: TypeError: array item must be char Which seems to happen repeatedly, i.e. it's not a passing error. While I'm here, a perhaps obvious question: where or how does the main Galaxy instance get the list of toolsheds to display? The main and test sheds are hardcoded in, I guess, but how does it pick up the local - simply by virtue of the fact that it is local? p ---- Paul Agapow (paul-michael.agapow@hpa.org.uk) Bioinformatics, Health Protection Agency ----------------------------------------- ************************************************************************** The information contained in the EMail and any attachments is confidential and intended solely and for the attention and use of the named addressee(s). It may not be disclosed to any other person without the express authority of the HPA, or the intended recipient, or both. If you are not the intended recipient, you must not disclose, copy, distribute or retain this message or any part of it. This footnote also confirms that this EMail has been swept for computer viruses, but please re-sweep any attachments before opening or saving. HTTP://www.HPA.org.uk **************************************************************************
Hi Paul, On Apr 10, 2012, at 9:15 AM, Paul-Michael Agapow wrote:
As per the title, I’m trying to setup a toolshed for our local use. After creating a repo, I try to upload the initial file only to get:
TypeError: array item must be char
Which seems to happen repeatedly, i.e. it’s not a passing error.
I'll need to see your paster log to be able to help on this one. You can view it using "tail -f community_webapp.log" (without the quotes) from your Galaxy install directory. Can you respond back with the content?
While I’m here, a perhaps obvious question: where or how does the main Galaxy instance get the list of toolsheds to display? The main and test sheds are hardcoded in, I guess, but how does it pick up the local – simply by virtue of the fact that it is local?
The list of tool sheds available to any local Galaxy instance is defined in the tool_sheds_conf.xml file in the Galaxy install directory. For your local shed, you'll simply need to an entry like this: <tool_shed name="Bx tool shed" url="http://gvk.bx.psu.edu:9009/"/>
p
---- Paul Agapow (paul-michael.agapow@hpa.org.uk) Bioinformatics, Health Protection Agency
Thanks, Greg Von Kuster
************************************************************************** The information contained in the EMail and any attachments is confidential and intended solely and for the attention and use of the named addressee(s). It may not be disclosed to any other person without the express authority of the HPA, or the intended recipient, or both. If you are not the intended recipient, you must not disclose, copy, distribute or retain this message or any part of it. This footnote also confirms that this EMail has been swept for computer viruses, but please re-sweep any attachments before opening or saving. HTTP://www.HPA.org.uk **************************************************************************
___________________________________________________________ The Galaxy User list should be used for the discussion of Galaxy analysis and other features on the public server at usegalaxy.org. Please keep all replies on the list by using "reply all" in your mail client. For discussion of local Galaxy instances and the Galaxy source code, please use the Galaxy Development list:
http://lists.bx.psu.edu/listinfo/galaxy-dev
To manage your subscriptions to this and other Galaxy lists, please use the interface at:
participants (2)
-
Greg Von Kuster -
Paul-Michael Agapow