Hi Ryan, I have tried to collect a minimal set of dependencies you need to have installed: https://wiki.galaxyproject.org/Admin/Config/ToolDependenciesList And we have a Galaxy Docker container that is working and should define and test a fresh Galaxy installation: https://github.com/bgruening/docker-galaxy-stable Please also have a look at the Galaxy playbook: https://github.com/galaxyproject/usegalaxy-playbook This defines a installation and deployment strategy of Galaxy for several platforms. I don't think that the Galaxy project is going to focus on one single platform. But this is only my opinion. I think one of Galaxy strength is, that it is working on everything besides Windows (without docker). Cheers, Bjoern Am 05.01.2015 um 23:36 schrieb Ryan G:
I hate to hijack this thread, but I was thinking about this over the holiday in how we are going to maintain a local up to date copy of Galaxy ourselves. One thought would be to standardize on a single supported platform aka an Amazon instance and make sure everything works on that single platform. This frees you from having to support many different platforms and versions. Have you guys given this some thought?
On Mon, Jan 5, 2015 at 12:05 PM, Nate Coraor <nate@bx.psu.edu> wrote:
Hi Michael,
I understand your frustration in this regard. We do make an effort to respond to and fix issues that people encounter when upgrading Galaxy releases. We've also made pretty significant strides in increasing the quality of our releases, including a feature freeze for at least 2 weeks prior to each release. The galaxy-dev mailing list is fairly active, as is our IRC channel (#galaxyproject on Freenode) for more real-time help.
If you're not familiar with the Galaxy News Briefs, these are the primary means of communicating the changes you should expect to see between Galaxy releases and any config changes that might be necessary between releases:
https://wiki.galaxyproject.org/DevNewsBriefs
We also recommend having a Test/QA Galaxy server (or cloning your production Galaxy instance) to test an upgrade before deploying it on your production instance(s) so most problems can be caught beforehand.
Unfortunately, due to the wide range of platforms, deployment scenarios, site-specific factors, and large scope of Galaxy functionality, we can't catch all potential issues. I don't think this is outside the rate typically experienced with major releases of large open source software, but it is still frustrating when it occurs. That said, we'll do our best to assist and improve documentation when you do encounter upgrade problems.
--nate
___________________________________________________________ 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/