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
Sorry - I fouled up and should have kept this on galaxy-dev.
-Scott
- Original Message -
>
> I'm forwarding this to galaxy-user instead of galaxy-dev.
>
> -Scott
>
> - Forwarded Message -
> From: "Scott McManus"
> To: "Sarah Maman"
> Cc: galaxy-dev@lists.bx.psu.edu
> Sent: W
I haven't been able to reproduce this yet with the instructions you
gave, but I'm not using the same environment. Can you give me an idea
of what tools you're using outside of SciPy/NumPy/Enthought stuff?
There is the possibility that the virtualenv.py script isn't being
sourced correctly. We ca
I've been told by Galaxy folks to keep this on galaxy-dev.
My apologies for any confusion.
-Scott
- Original Message -
>
> Hi Dan-
>
> Thanks again for your great hospitality at UCI!
>
> It looks like you've done most of the sane things, and a quick
> check looks like the PBS egg is r
Hi Dan-
Thanks again for your great hospitality at UCI!
It looks like you've done most of the sane things, and a quick
check looks like the PBS egg is requesting protocol version 1
while the server supports protocol version 2. One possibility
is that there is a protocol mismatch, which could be
Hi Sarah-
I'm sure others have experiences that could help, so I hope they will
chime in. Nate put together some slides two years ago on production setups,
including some architecture for the server main.g2.bx.psu.edu:
http://wiki.g2.bx.psu.edu/Events/GDC2010?action=AttachFile&do=get&target=GDC20
Clare-
Have you resolved this yet? I had seen similar issues with respect
to pycrypto before I used virtualenv, but I don't believe that I saw
it afterwards. I'll take a look and see if I can reproduce it.
I only have obvious things to recommend right now. For example,
make sure that the environ
Hi Makis,
This should work to get you an update-able galaxy instance going forward,
without having to manually migrate anything.
Please note that this method will clobber any existing changes to code, so if
you've modified any of the core galaxy you'll need to patch the new files. All
of your
Hi Shaun,
Thanks very much for the details - they have helped me discover a weakness
which I've fixed. if the browser page is opened to the "Manage repository"
page in the tool shed when the repository is cloned for the first time, the
repository name could be changed after the clone. This ha
Hello again,
I've read on the mailing list that some galaxy users are facing the same
problem as I do, and that it seems to be related to the internet browser.
Indeed, I noticed that I have no problem uploading data while using IE 8 or 9,
but that it almost never works with Firefox, Chrome or
I finally wrote a script which can be used as a separate tool. The script takes
one or more file paths which
can be either a file or a directory.
As soon as the script does not know the exact number of files to "upload" it
places links to the files in
__new_file_path__. The problem now is, tha
Hi Shaun,
On Aug 1, 2012, at 6:13 AM, SHAUN WEBB wrote:
>
>>>
>>> c) The toolshed interface allows me to change the name of my tool. If I do
>>> this, then go to my Galaxy admin ui and try to get updates for my tool then
>>> it fails. Does it make sense to change a tools name after it is crea
Hi Greg, thanks for the response
Quoting Greg Von Kuster on Tue, 31 Jul 2012 11:50:36 -0400:
Hi Shaun,
On Jul 31, 2012, at 9:37 AM, SHAUN WEBB wrote:
Hi, I have been trying out the latest version of Galaxy and a newly
installed local toolshed and I have a few questions/suggestions/bug
13 matches
Mail list logo
