Thank you very much for sharing Youssef. Very helpful.

Martin

On Fri, Oct 21, 2016 at 10:20 AM Youssef GHORBAL <youssef.ghor...@pasteur.fr>
wrote:

> Hello,
>
>         Two other tables need to be adapated (they reference tool_id)
>         Table “job" and table “workflow_step”
>
> Youssef Ghorbal
> Institut Pasteur
> -----------------
> > On 21 Oct 2016, at 00:36, Youssef Ghorbal <youssef.ghor...@pasteur.fr>
> wrote:
> >
> > Hello,
> >
> >       What worked for us was this action sequence :
> >       - stop Galaxy
> >       - update config/tool_sheds_file.xml (change the URL from the old
> one to the new one)
> >       - “sed” shed_tool_conf.xml to change the “guid", the tool_shed and
> the “file” to replace the old prefix with the new prefix.
> >       - update the tool_version table (the tool_id column) to change the
> old prefix to the new prefix.
> >       - update the tool_shed_repositoriy table to change the tool_shed
> column to use the new tooshed prefix
> >       - update the directory shed_tools to rename the directory from the
> old prefix to the new prefix (care to adapt the subdirectories too :
> ./mytoolshed.url/xxx => ./mytoolshed2.url/yyyy)
> >       - start Galaxy (and cross your fingers)
> >
> >       Hope this help !
> >
> > Youssef Ghorbal
> > Institut Pasteur
> > -----------------
> >> On 20 Oct 2016, at 00:16, Youssef GHORBAL <youssef.ghor...@pasteur.fr>
> wrote:
> >>
> >> Hello,
> >>
> >>      I’m wondering if there is any way to change an established Tool
> Shed URL.
> >>      I have a Galaxy instance and a Tool Shed instance (
> http://mytoolshed.url/xxx) A lot of tools have beed installed from that
> Tool Shed inside Galaxy (tools referenced inside workflows etc)
> >>      I want to change the Tool Shed URL from http://mytoolshed.url/xxx
> to http://mytoolshed2.url/yyyy.
> >>
> >>      Galaxy and Tool Shed seems to use parts of the URL as a guid for
> tools.
> >>
> >>      Tool Shed does not seem to bother to be called by either URLs (it
> generates guids with the new URLs scheam for new tools though)
> >>
> >>      Galaxy does not seem to handle it, I changed the
> tool_sheds_conf.xml to point to new URL, but when I update a tool on the
> Tool Shed, Galaxy gets the new version but it generates buggy tool panel
> (the tool is cited twice)
> >>      I also tried to mess around with the shed_tool_conf.xml apdapting
> the guids and the <tool_shed> items with no luck.
> >>
> >>      Can someone point me to the right direction ? How the matching is
> done between shed_tool_conf.xml entries, the tool_version and
> tool_shed_repository tables.
> >>
> >>      Thank you for your help.
> >>
> >> Youssef Ghorbal
> >> Institut Pasteur
> >> ___________________________________________________________
> >> 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:
> >> https://lists.galaxyproject.org/
> >>
> >> 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:
>   https://lists.galaxyproject.org/
>
> 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:
  https://lists.galaxyproject.org/

To search Galaxy mailing lists use the unified search at:
  http://galaxyproject.org/search/mailinglists/

Reply via email to