Not really sure what is happening here, does your galaxy.ini file have
the following sections:
[filter:proxy-prefix]
use = egg:PasteDeploy#prefix
prefix = /galaxy
[app:main]
filter-with = proxy-prefix
cookie_path = /galaxy
If yes, it might be best to share nginx configuration and your galaxy
Ryan,
Not sure what the problem is. I'm not sure the Galaxy that is
distributed with Biolinux is really setup to be used with PBS/Torque.
If you have pbs/torque installed and running properly and if you can
submit job scripts via the qsub command as whatever user Galaxy runs
under - the
Dear all,
I have a problem with configuring my galaxy instance with a proxy server when
I try to serve at a subdirectory.
I followed the description at
https://wiki.galaxyproject.org/Admin/Config/nginxProxy
The basic configuration works just fine.
When I use the procedure described in the
When I've seen similar behavior in the past, it's always that cookie_path
is incorrect.
On Thu, Aug 27, 2015 at 1:46 PM, John Chilton jmchil...@gmail.com wrote:
Not really sure what is happening here, does your galaxy.ini file have
the following sections:
[filter:proxy-prefix]
use =
Hi Carl,
Thank you for your help, I was able to access all the dataset ids in
history with the pointers you gave, but I am not finding an immediate way
to deduce which original file is from which id. I think if I can get the
timestamp of the datasets I can use this and the dataset type metadata.
So it wasn't in 15.01 - it was before that but the local job runner
was changed to set metadata as part of the job (I think probably
sometime in 2014). When it was setting metadata externally it might
have used slightly different dependency resolution strategies that
would result in samtools being
I don't think there is a way given the implementation. The name of the
association is repeatname_0|input1 but the | is treated as a special
symbol so it won't be used to get the parameter.
I have opened a PR to allow this:
https://github.com/galaxyproject/galaxy/pull/662
The syntax in the
Hi Bjoern
thanks for the reply. I previously did not find this in the API documentation
but had a look now again
(http://galaxy.readthedocs.org/en/master/api_doc.html#module-galaxy.webapps.galaxy.api
http://galaxy.readthedocs.org/en/master/api_doc.html#module-galaxy.webapps.galaxy.api)
and
