Hi,
I'm currently using one of those hacks, and it seems to work nicely for
the user (Chrome + FF at least) but it does need some messy setting up
in Apache and some cunning redirects in place. I've pasted the relevant
file fragments below. It's somewhat confounded with my stuff to enable
SFTP
Hi Eric,
Thanks for reporting this error, it has been resolved in changeset
12278:04bce95d8fd2 and 12281:6c5913a4b701. Please let us know if you encounter
additional issues.
Thanks for using Galaxy,
Dan
On Jan 27, 2014, at 4:56 AM, Eric Kuyt eric.ku...@wur.nl wrote:
Hi Greg or James,
I don't know of a way to accomplish what you are describing with the
tool framework - without prepopulating static files with all of the
data you will need - and even then I am not exactly sure what to do.
But it sounds like you would like to fetch this data from a database
or web service of some
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi Tim,
Amazing! Thank you for sharing that code. That'll save me some work when
I get around to implementing it on my galaxies. I'll add a Wiki page for
it later today, lest this knowledge be lost to the mailing list.
Cheers,
Eric
On 01/27/2014
dear all,
When I try to install a tool from our local toolshed Galaxy changes the
repository url from HTTPS to HTTP and throws an error.
I'm setting up a local (intranet) toolshed for some of our in house tools.
We run galaxy (latest stable) on HTTPS://nioo0025.nioo.int/galaxy
The toolshed is
I have attached a patch to disable this. The swap over happens when
the number of items gets sufficiently large and a jQuery-based widget
called select2 replaces all select boxes in Galaxy - unless explicitly
disabled. I understand the desire to disable this. I am not sure
anyone is really very
Hi everybody,
I managed to configure Galaxy to work with DRMAA in our cluster but after the
job finished, the dataset state is set to error. Here is the last few lines of
the paster.log file:
galaxy.jobs.runners.drmaa DEBUG 2014-01-27 10:52:50,449 (181) submitting with
credentials: jing
Hi Eric, Tim,
Hi Tim,
Amazing! Thank you for sharing that code. That'll save me some work when
I get around to implementing it on my galaxies. I'll add a Wiki page for
it later today, lest this knowledge be lost to the mailing list.
That is an excellent suggestion. I've created a log
So I tried a new version of ProFTPd
I was not able to locate lines in universe_wsgi.ini which disable PBKDF2
Lines from SQLLogFile.txt
2014-01-21 18:09:33,191 mod_sql/4.3[2275]: checking password using
SQLAuthType 'sha1'
2014-01-21 18:09:33,191 mod_sql/4.3[2275]: 'sha1' SQLAuthType handler
The main Galaxy Tool Shed is now running the next-stable branch in preparation
for the next Galaxy release tentatively scheduled for 2 weeks from today. The
current changeset revision on the main Tool Shed is:
changeset: 12285:3fdf673bdfc9
branch: next-stable
Complete documentation for
Hello Shivani,
The problem is either related to 3rd party cookies being enabled or a
missing configuration in the universe.wsgi.ini file. This thread, in the
second part, provides the full solution:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I figured this was as good of a time as any...
I moved the AD/LDAP/External authentication out of the Apache Proxy page
(who would think to look there?) and into its own page. I added my
organisation's information on mod_auth_kerb while I was at it.
On Jan 27, 2014, at 9:57 AM, John Chilton chil...@msi.umn.edu wrote:
The swap over happens when
the number of items gets sufficiently large and a jQuery-based widget
called select2 replaces all select boxes in Galaxy - unless explicitly
disabled. I understand the desire to disable this. I am
Is there a data type in Galaxy that identifies executables uniquely, eg.
from the executable bit in the file perms or some other way?
Thanks,
--
Ketan
___
Please keep all replies on the list by using reply all
in your mail client. To
14 matches
Mail list logo
