Hi John,
I see that in my last email I replied to you with the fourth (and not the
third) option in mind :(.
Just to come back to this related to the third option (i.e. Have a dummy tool
to produce a settings file and allow the users to choose this file when running
the real tool): I don't
Dear all,
I'm trying to migrate our local Galaxy server from a standalone server running
on CentOS 5 to a setup that runs Galaxy in a Docker container
(bgruening/galaxy-stable). Due to Docker and the setup of the container, almost
all data, tools, configs etc. have to move to a different
Hmm hopefully someone more knowledgeable about the tool shed than
me responds also but I had a couple quick thoughts.
The first is a warning - workflows may break. At very least workflows
that depend on the previous instance having gone through tool
migrations instead of tool install. My
Hello galaxians,
I'm currently trying to set up a production galaxy and make it available to
the public but I face a weird issue, probably because of my nginx proxy
configuration.
Galaxy is on a kvm virtual machine running on a host using nginx as proxy.
to make it a bit clearer:
172.30.24.35
Dear John,
thank you very much your help and the warnings!
I'm testing it with a second database and so far it seems to work :-).
I was also suspecting the encoding to be the issue, that's why I did it through
pg_dump and specified the encoding of the new server for the dump. The error
stayed
Hi all,
Is it possible to read id's from a column of an input dataset and
create a checkbox parameter with the unique id's of that column within
the same tool?
The only remotely similar action that I found is on the sorting tool
where it reads the number of the columns of that dataset and
Hello all,
We are pleased to announce the *Galaxy Training Network (GTN)
https://wiki.galaxyproject.org/Teach/GTN*, a network of trainers who
teach bioinformatics using Galaxy, or teach about Galaxy itself. The GTN
aims to make it easy to find Galaxy trainers
Hi folks,
I encountered the problem in file upload. The error message is like below
'Failed: Not found (404)'. Attached is the screen shot for this error
message. Any idea? Thanks!
Best,
Bongsoo
___
Please keep all replies on the list by
Hi,
this is just to make sure: the GALAXY_SLOTS environmental variable set
by Galaxy when running tools will always be a number = 1 with 1 being
the default if nothing else is configured in the job runner settings ?
Correct ?
Thanks,
Wolfgang
Hey Bongsoo,
Does this happen on usegalaxy.org? Also does this happen with other files
too?
Thanks,
Sam
On Thu, Oct 16, 2014 at 2:49 PM, Bongsoo Park bx...@psu.edu wrote:
Hi folks,
I encountered the problem in file upload. The error message is like below
'Failed: Not found (404)'. Attached
Aysam,
Thanks for your reply. It works well on usegalaxy.org, but it doesn't work
in the Galaxy instance I've developed. I downloaded the latest Galaxy
version, and installed on the Redhat 6.5 system. I created a galaxy user,
and just ran it as usual. I have to update any part of the
Hi Wolfgang,
\${GALAXY_SLOTS:-4} in this case will default to 4 if you have not
configured it in job_conf.xml. Otherwise yes, it will be 1.
Ciao,
Bjoern
Am 17.10.2014 um 00:05 schrieb Wolfgang Maier:
Hi,
this is just to make sure: the GALAXY_SLOTS environmental variable set
by Galaxy when
No it is not. The thinking was that autoscaling should be responsive and
spot instance are not necessarily predictable so we decided against it. We
can revisit that idea though if you're keen?
Cheers,
Enis
On Wed, Oct 15, 2014 at 11:05 AM, Petit III, Robert A.
robert.pe...@emory.edu wrote:
13 matches
Mail list logo