Hi Does anyone have any experience or advice about running two servers on the same database?
The pros are that I can test tools and some other changes against actual datasets and check bug fixes directly by giving users temporary access to a dev server so that they regress the bugs themselves. The cons are that I risk damaging user data and ending up with a pile of rubble. I would like to have a production server and development server both running simultaneously. There are obvious issues such as the schema needs to be compatible for both systems simultaneously. This might mean disabling or enhancing the schema version control mechanism. What else needs to be modified to make this work? As the wicked witch of the west said "these things must be done very del-i-cate-ly" ;-) Thanks, Ted ___________________________________________________________ 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/ To search Galaxy mailing lists use the unified search at: http://galaxyproject.org/search/mailinglists/
