Our data is backup and we are planning to shutdown the galaxy for moving
data to the new place, change the file_path value in universe config, then
start the galaxy again.
My only concern is if the existing value of file_path get hard-coded in the
On Thu, Feb 14, 2013 at 8:47 PM, Peter Cock <p.j.a.cock(a)googlemail.com>wrote:
We did that a year ago, while changing the mount point as
part of setting up a shared file system between our Galaxy
node and a cluster. Naturally we did a backup first, but I
don't recall any issues from this. At the time Nate just advised
not to have any jobs running at the time (and stop Galaxy of
On Thursday, February 14, 2013, Derrick Lin wrote:
> Hi Shantanu,
> We are facing the same situation that migrating galaxy dataset to a new
> location is needed. I am wondering if you have done it successfully? Would
> be nice if you can share your experience with us.
> On Fri, Nov 30, 2012 at 9:21 AM, Shantanu Pavgi (Campus) <pavgi(a)uab.edu>wrote:
>> We are planning to change datasets directory location (file_path setting
>> in universe_wsgi.ini) in our Galaxy installation. We will be moving
>> existing datasets to the new directory location and updating XSendfile
>> setting in Apache as well. I was wondering if there are any side effects
>> that we should be considering before making this change. There are certain
>> fields in the database (e.g. command_line in jobs table) which contain
>> absolute path of datasets. Do we need to update any of these fields to make
>> sure Galaxy is functional after file_path is changed?
>> 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: