Hi Nate,
My "solution" was a bit of a hack and there may be better ways of doing it (I
haven't read all the docs yet - just started with Galaxy last week)
Python is not my strong suit and there may be more elegant ways, but here's how
I usually connect thru our proxy:
---
I had a similar problem where $PATH doesn't appear to be getting read but mine
was with the EMBOSS packages.
I cheated a bit and just put the full path for the executables in the command:
perl -npi -e 's::/usr/local/bin/:' emboss_*.xml
--Russell
> -Original Message-
> From: galaxy-dev-b
Hi,
I've put the executable in the directory where the xml file and wrapper is. The
message I'm getting when I run the tool is Unable to run tool: No such file or
directory.I guess that I'm forgetting something
> Subject: Re: [galaxy-user] Upload executable in galaxy
> From: n...@bx.psu.e
This may be a list of weird requests but our Galaxy server runs internally and
is only accessible to our users so I'd like to make it a bit easier to manage.
I could customize a copy but hopefully some of the "features" I'm after are
already available. If not, I'm happy to work on them and integr
Hi Russell,
Just addressing AD/LDAP authentication - authentication is trivially and
best (IMHO) left to an external (eg apache) proxy - save yourself a lot of
effort - it's known to work well.
Lock down the paste process so it only talks to your apache and provide
pass through authentication.
Doi
Thanks Enis! It's not a problem for our current task, but it would be
a nice feature.
On Thu, Dec 1, 2011 at 8:38 PM, Enis Afgan wrote:
> Unfortunately not. When removing nodes, CloudMan chooses from the nodes that
> are currently not being used but among those the choice is random.
> You can ma
There is some documentation on the wiki. You need to modify the designated .loc
file.
It has explained here on a BioStar qustion:
http://biostar.stackexchange.com/questions/15035/custom-blast-db-on-galaxy-server
Alex
-Oorspronkelijk bericht-
Van: galaxy-dev-boun...@lists.bx.psu.edu
[mail
