Hi Chris, As long as the two instances are running the same version of the Galaxy code, and you do not have "track_jobs_in_database" turned on in your config, this should work fine. Particularly if your live instance has a subset of the tools that the development instance has. On the other hand, running different versions of the Galaxy application against the same database is probably mad. We occasionally make schema changes that are automatically applied to the database at startup, but if an older instance is still looking at the same database... potential disaster. Thanks, James On Oct 29, 2008, at 12:59 PM, Chris Cole wrote:

What is the best way to work with development and live versions of Galaxy concurrently and being able to have access to the same data (e.g. user histories)?

Currently, I'm trying to run two instances of galaxy at the same time using the same MySQL database back-end and pointing to the same user files (via softlinks). Does this way madness lie? Although, it does seem to be working...

I'm asking this because if we do go down the route of deploying Galaxy here, we'd like to be able to be able to test new tools without constantly having to restart the server and annoy the users. Cheers,

Chris _______________________________________________ galaxy-user mailing list galaxy-user@bx.psu.edu http://mail.bx.psu.edu/cgi-bin/mailman/listinfo/galaxy-user