On Thu, Sep 2, 2010 at 3:10 PM, Hans-Rudolf Hotz <hrh@fmi.ch> wrote:
Peter
not really a version number, but I recommend to follow the "News Briefs"
http://bitbucket.org/galaxy/galaxy-central/wiki/Features/DevNewsBriefs
That's useful. Does this also get sent out by email, or on a news server with RSS/Atom feeds? I don't want to have to manually check the wiki every month.
yes, you will get an e-mail via [galaxy-dev], for example see:
http://lists.bx.psu.edu/pipermail/galaxy-dev/2010-August/003173.html
Lovely :)
For us, adding our own tool is the big thing about Galaxy and we are pretty happy with the default Galaxy distro. Of course we have a few customizations, but they are added very quickly to a new 'release' by hand.
Could you clarify how you update your Galaxy install via hg, specifically regarding preserving local configuration changes and extra tools?
In our case, we update our production server every three month with "hg pull" (last time we did "hg pull -u -r -u - 837aabec314e" , pulling from http://bitbucket.org/galaxy/galaxy-dist/).
Local customizations in file like 'lib/galaxy/datatypes/registry.py' or 'lib/galaxy/datatypes/sequence.py' are nicely merged.
"conflicts", which might happen in files like 'static/welcome.html' can be resolved during the upgrade process.
Your own tools and tool description files are not touched. I would put them in a separate folder, just to be on the safe side
And at the end I manually fix the file universe_wsgi.ini
Do you check in any of your local changes into the local hg repository?
I recommend, start playing with galaxy, add your own tools, do an update a few weeks later, and you will see: It is really not rocket science. The galaxy developers do a great job providing a stable and simple system.
I'm sure I'll manage - its just this repository based distribution/install system which runs in situ is a bit unusual for me (plus I don't yet know much about using hg/mercurial). Peter