I wrote something in Python a while back (which I've attached) to parse a
shed_tool_conf.xml file and generate a shell script to install those tools
on a different server. The shell script uses Galaxy's
scripts/api/install_tool_shed_repositories.py to install the tools and ends
up looking something
Hi Peter
Thanks for your comments - at least it doesn't sound like I'm missing
the "perfect" way to migrate the installed tools. In the longer term
moving towards bioconda dependency resolution will probably be more stable.
Also re breaking tool repos: even repos that aren't updated on the
t
On Wed, Nov 23, 2016 at 10:49 AM, Peter Briggs
wrote:
> Hello Evan, Hans-Rudolf
>
> I'm just in the middle of doing a similar migration for our local production
> server, and Hans-Rudolf's advice seems sound to me. Definitely moving the
> core Galaxy server has been relatively straightforward.
>
>
Hello Evan, Hans-Rudolf
I'm just in the middle of doing a similar migration for our local
production server, and Hans-Rudolf's advice seems sound to me.
Definitely moving the core Galaxy server has been relatively
straightforward.
However: for the installed tools, I'm not sure that changing
Hi Evan
Well, in theory, this is a simple task, since Galaxy mostly works with
relative paths. Of course, it all depends on how sophisticated your
installation is and how different the old and the new 'machine' is (eg
same OS?)
So my advice is: just do it or rather try it.
- make a copy of
Is there a good method for moving a fully functional galaxy install from
one machine to another in a different directory?
___
Please keep all replies on the list by using "reply all"
in your mail client. To manage your subscriptions to this
