Just to follow up on this - you will want to explicitly check dataset.external_filename in your database for any hard coded paths that may have changed.

Also - all tool shed installed tools including migrated tools are creating tool dependency files (env.sh) in tool_dependency_dir that contain hard coded paths. These will all need to be updated.

I imagine some tools will no longer work after migration - for instance anything installed with virtualenv :(. These will likely need to be reinstalled. I wish I could say I thought that was going to be an easy process.

Good luck.

-John

On Jan 17, 2014 2:13 AM, "Hans-Rudolf Hotz" hrh@fmi.ch wrote:

Hi Ido

Over the last few years, we have moved our production server to different hardware twice. And we also made copies of our production server in order to have the right development environment.

It always work without much hassle, once we have taken care of the 'obvious', which usually was a combination of changing the absolute paths the configuration files and creating sym-links.

As always, make sure you have a back-up of your PostgreSQL (or MySQL) database.

Regards, Hans-Rudolf

On 01/16/2014 02:43 PM, Ido Tamir wrote:

...

Hi,

I have to move my galaxy instance to a different file system location. Is there anything that I have to look out for besides the obvious like absolute paths in some data configs?

thank you very much, ido

---

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/

---

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/