10 months ago by
In theory, an update should be possible despite the fact that Galaxy has changed from mercurial to git in 2015. Have a look at:
Once you have changed, you can then do the actual update.
Depending on how many and what kind of local changes you've done in the Galaxy code, you might wanna consider a different approach:
- install a fresh, up-to-date Galaxy server
- point this new server to a copy of your (PostgreSQL) database, and run 'manage_db.sh upgrade'
- copy the 'database' directory (i.e. all the datasets) from your existing server to the new server
- add your local changes, like '.loc' files, '~/tool-data/shared/ucsc/chrom/.len' files, etc
- add your local changes to 'galaxy.ini' (this is the replacement of the 'universwgs.ini' file), like add the admin users, etc
- add the required tools from the toolshed
- add your local (non-toolshed) tools
- try whether it works....
I have done this kind of approach last year. Though, I only had to switch from (mercurial) version 15.10 to (git) version 16.04, but it involved a hardware change and system software change.
Whatever way you gonna try, make sure you have a solid backup of both the complete galaxy directory tree and the (PostgreSQL) database.
Hope this helps