Neil, If by 'multiple' you mean 'independent' galaxy instances, they must each talk to independent backend databases, so if you're thinking of running eg 2 or more independent instances at CSIRO, each for specific tool sets and sending each of your users to one or other of them based on some smart Apache code and their login, beware that users won't be able to share or see any histories or datasets from one instance on the other.
That might work well - or not - but separate instances cannot safely share the same backend database tables - they're just separate Galaxy instances - like test and main are, and there's no specific documentation needed. If you are asking about multiple processes (web servers etc) to scale up a slow heavily loaded instance, that's documented in the wiki - eg a quick search finds http://wiki.galaxyproject.org/Admin/Config/Performance/ProductionServer?action=show&redirect=Admin%2FConfig%2FPerformance On Fri, Feb 8, 2013 at 1:40 PM, <neil.burd...@csiro.au> wrote: > Hi,**** > > Can someone point me to the documentation to set up /configure multiple > instances of Galaxy running on the same node please?**** > > ** ** > > I think this is the best method of hiding tools based upon users email > logon...**** > > ** ** > > Thanks**** > > Neil**** >
___________________________________________________________ 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: http://lists.bx.psu.edu/