the Galaxy interface. What
> should I do to create this AMI?
>
> Thanks,
> Jose
>
> > Subject: Re: [galaxy-dev] CloudMan: Command not found
> > From: dannonba...@me.com
> > Date: Wed, 13 Jun 2012 21:32:24 -0400
>
> > CC: galaxy-dev@lists.bx.psu.edu
> > T
tools through the Galaxy interface. What should I
do to create this AMI?
Thanks,Jose
> Subject: Re: [galaxy-dev] CloudMan: Command not found
> From: dannonba...@me.com
> Date: Wed, 13 Jun 2012 21:32:24 -0400
> CC: galaxy-dev@lists.bx.psu.edu
> To: josenavasmol...@hotmail.com
>
&g
t;
> thanks!
>
> Jose
>
> > Subject: Re: [galaxy-dev] CloudMan: Command not found
> > From: dannonba...@me.com
> > Date: Wed, 13 Jun 2012 21:05:02 -0400
> > CC: galaxy-dev@lists.bx.psu.edu
> > To: josenavasmol...@hotmail.com
> >
> > Instead
Hi Dannon,
thank you for your help. I've tried the tag option with the
'env.sh' script. I have added ~100 XML files... there isn't any option to
modify the environment variables directly? If not I will modify all my XML
files
thanks!
Jose
> Subject: Re: [galaxy-dev
Instead of modifying the environment variables directly, I've found it easier
to use Galaxy's built in tool dependency framework. All you'd have to do is
add a tag to your custom tools to specify the
package directory that needs to be checked at runtime.
See http://wiki.g2.bx.psu.edu/Admin/Co
Hi Galaxy Team,
I'm modifying my Galaxy CloudMan instance by adding custom tools. I've
installed my tools under the /mnt/galaxyTools/tools folder and I've modified
the .bashrc files from the sgeadmin and galaxy users to add the needed paths to
the PATH and PYTHONPATH variables. When I'm in Gala
