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 the paths
in the env.sh files is sufficient - in our installation the absolute
paths seemed to be baked into a lot of other files under the
'tool_dependencies' directory - including things like compiled files
(e.g. static and shared libraries). So for many of the tools I wouldn't
feel confident that they would still work after the move.
My plan has been to reinstall each of the tools from the toolshed (i.e.
uninstall via the admin interface then reinstall the same tool
repository revision(s) using the API), but I don't feel able to
recommend this approach either as in my testing this has also had
problems - ranging from some tool revisions no longer being available,
through to more serious issues (such as tool dependencies which used to
work but since become broken). I figured I'd just have to knuckle down
and work through each problem as I encountered it.
If anyone else has experiences with these kinds of migrations then I'm
also very interested to know what worked (and what didn't)!
Best wishes
Peter
On 23/11/16 08:20, Hans-Rudolf Hotz wrote:
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 your installation on the new hardware (at first it is
sufficient to copy only the latest sub directories of database/files/)
- make a copy of your PostgreSQL database
- connect your copied installation to the PostgreSQL database copy and
test, and test, and test
- pay special attention to tools you have installed via the toolshed.
You might need to change some absolute paths in the 'env.sh' files
located in the tool_dependencies/ directory.
Once your happy with all the tests, do an rsync on the database/
directory and connect to the original PostgreSQL database.
Regards, Hans-Rudolf
On 11/22/2016 07:52 PM, evan clark wrote:
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
and other Galaxy lists, please use the interface at:
https://lists.galaxyproject.org/
To search Galaxy mailing lists use the unified search at:
http://galaxyproject.org/search/mailinglists/
___________________________________________________________
Please keep all replies on the list by using "reply all"
in your mail client. To manage your subscriptions to this
and other Galaxy lists, please use the interface at:
https://lists.galaxyproject.org/
To search Galaxy mailing lists use the unified search at:
http://galaxyproject.org/search/mailinglists/
--
Peter Briggs peter.bri...@manchester.ac.uk
Bioinformatics Core Facility University of Manchester
B.1083 Michael Smith Bldg Tel: (0161) 2751482
___________________________________________________________
Please keep all replies on the list by using "reply all"
in your mail client. To manage your subscriptions to this
and other Galaxy lists, please use the interface at:
https://lists.galaxyproject.org/
To search Galaxy mailing lists use the unified search at:
http://galaxyproject.org/search/mailinglists/
