Hi Wolfgang
short answer:
Please, put your package into the Galaxy Tool Shed. This makes it
visible to the whole Galaxy community and everybody can profit from it.
long answer:
I have been in the same boat. We never put the Galaxy wrappers and the
perl scripts of our old NGS pipeline
Hmm... sorry for the delay I hope you got this to work. I feel like
someone should respond to this but it is difficult to remotely debug
web server configuration issues.
Should your apache config line:
RewriteRule ^(.*) http://localhost:8080$1 [P]
be:
RewriteRule ^/galaxy(.*)
Hi John,
your solution perfectly solved my problem.
Thank you!
-Ursprüngliche Nachricht-
Von: John Chilton [mailto:jmchil...@gmail.com]
Gesendet: Friday, June 06, 2014 3:32 PM
An: Matthias Enders
Cc: galaxy-...@bx.psu.edu
Betreff: Re: [galaxy-dev] Installing galaxy with Apache
Hmm...
I was wondering if there is a possibility of a 'Tool'Shed for
Visualisation registry plugins(custom plugins, developed by
users/developers)?
The motivation for this comes from a small 'tool' I wrote for
visualiing fastq phred scores using box plots[Still under development]
here:
Hello Saket,
Thanks for your interest - I totally agree, I think a lot of tools
like this would be better served as visualization plugins. There is a
Trello card for this request https://trello.com/c/YLA70rZx - please
vote up if you are interested.
This has been discussed by the core team and I
Thanks a lot for all the encouraging feedback.
More than anything else the friendly atmosphere that seems to prevail on
this mailing list makes me think that it may indeed be worthwhile to
make the package available to this community !
I will have a closer look at the toolshed instructions and
Hi Malcolm,
That error makes me think you might be running an outdated version of
galaxy code - the toolshed code has undergone extensive revision over the
last few months?
I just tested that repository on a freshly updated galaxy-central clone and
it installed without drama, so I wonder what:
hg
Hi folks,
We're working on developing a VM which we'd like to be tightly coordinated
with Galaxy, such that VM users can export data from the VM into Galaxy,
perform further analyses on that data, and then import the analysis results
into the VM for storage (from where it will serve additional
Hi Melissa,
The question in the title is easy to answer - most large galaxy instances
run (most) jobs on a connected cluster which is effectively 'background' I
guess so yes - all of them on cluster backed Galaxy instances might be a
reasonable response.
The questions in the text are more
