ok - sorry I misunderstood. Yes, assuming you already have one Galaxy instance configured right, cloning and editing the rewrite and authentication sections for the other paste process should work and that looks reasonable to me FWIW - OTOH, apache configuration is definitely one of the darker arts so the only way to tell is to run them and keep an eye on the two separate paste process logs as you hit each site separately.
Of course, make sure the indepndent instance universe_wsgi.xml files specify independent postgresql databases and keep the two independent galaxy file store directories separated or very bad things will happen. On Fri, Feb 8, 2013 at 2:20 PM, <neil.burd...@csiro.au> wrote: > Thanks Ross.**** > > ** ** > > I did mean separate Galaxy instances like test and main with their own > independent backend databases.**** > > ** ** > > How could I run say a test and a main from the same node? **** > > ** ** > > I guess I’d need to modify the port number for each instance and then > multiple entries in the apache config file i.e. So they show physically > separate information when loaded... i.e. http://localhost/galaxyTest and > . http://localhost/galaxyMain**** > > ** ** > > *RewriteEngine* *on***** > > *RewriteRule* ^/galaxyTest$ */galaxyTest/* [R]**** > > *RewriteRule* ^/galaxyTest/static/style/(.*) * > /home/nate/galaxy-dist-test/static/june_2007_style/blue/*$1 [L]**** > > *RewriteRule* ^/galaxyTest/static/scripts/(.*) * > /home/nate/galaxy-dist-test/static/scripts/packed/*$1 [L]**** > > *RewriteRule* ^/galaxyTest/static/(.*) * > /home/nate/galaxy-dist-test/static/*$1 [L]**** > > *RewriteRule* ^/galaxyTest/favicon.ico * > /home/nate/galaxy-dist-test/static/favicon.ico* [L]**** > > *RewriteRule* ^/galaxyTest/robots.txt * > /home/nate/galaxy-dist-test/static/robots.txt* [L]**** > > *RewriteRule* ^/galaxyTest (.*) http://localhost:9080$1 [P]**** > > ** ** > > *RewriteRule* ^/galaxyMain$ */galaxyMain/* [R]**** > > *RewriteRule* ^/galaxyMain/static/style/(.*) > */home/nate/galaxy-dist-main/static/june_2007_style/blue/*$1 [L]**** > > *RewriteRule* ^/galaxyMain/static/scripts/(.*) > */home/nate/galaxy-dist-main/static/scripts/packed/*$1 [L]**** > > *RewriteRule* ^/galaxyMain/static/(.*) > */home/nate/galaxy-dist-main/static/*$1 [L]**** > > *RewriteRule* ^/galaxyMain/favicon.ico > */home/nate/galaxy-dist-main/static/favicon.ico* [L]**** > > *RewriteRule* ^/galaxyMain/robots.txt > */home/nate/galaxy-dist-main/static/robots.txt* [L]**** > > *RewriteRule* ^/galaxyMain (.*) http://localhost:9081$1 [P]**** > > ** ** > > Is that correct?**** > > ** ** > > Cheers**** > > Neil**** > > ** ** > > ** ** > > *From:* Ross [mailto:ross.laza...@gmail.com] > *Sent:* Friday, 8 February 2013 12:54 PM > *To:* Burdett, Neil (ICT Centre, Herston - RBWH) > *Cc:* email@example.com > *Subject:* Re: [galaxy-dev] Multiple Instances ...**** > > ** ** > > 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**** > > ** > -- Ross Lazarus MBBS MPH; Head, Medical Bioinformatics, BakerIDI; Tel: +61 385321444 http://scholar.google.com/citations?hl=en&user=UCUuEM4AAAAJ
___________________________________________________________ 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/