I'm not sure if it would be a patch, or what. the last communication we had on this was from Lincoln on July 31 in which he stated ( to Todd Harris ):
----
I've added a new option to the gbrowse config file that will let you work around the web proxy problem. In the [general] section, please set "galaxy incoming" to the URL to use for the gbgff script installed on the wormbase gbrowse backend. I think this is right:

galaxy incoming = http://www.wormbase.org/db/seq/gbgff

You will also want to set the "galaxy outgoing" option to point at the live Galaxy server. I think this is right:

galaxy outgoing = http://main.g2.bx.psu.edu/
-----

So, if there's a GMOD ( C Elegans ) server that is configured with this GBrowse fix, perhaps all we need is a URL.

David M. Goodstein wrote:

So you're waiting on a patch to the 1.69 release?
David M. Goodstein

Joint Genome Institute / Lawrence Berkeley National Lab

Center for Integrative Genomics / UCBerkeley
On 12 Dec 2008, at 13:18, Greg Von Kuster wrote:
GBrowse version 1.69 was configured to communicate with Galaxy, but when it was moved to one of the GMOD production servers some configuration issues were discovered and some corrections were needed. The Galaxy team is waiting on confirmation that the issues have been resolved, and what server to point to specifically for the C Elegans tool that's included in the Galaxy distribution.

Greg Von Kuster
Galaxy Development Team

David M. Goodstein wrote:
Specifically the ability to pull and push data to/from Galaxy to a Gbrowser?

thx,

--David

David M. Goodstein

Joint Genome Institute / Lawrence Berkeley National Lab

Center for Integrative Genomics / UCBerkeley
_______________________________________________
galaxy-dev mailing list
galaxy-dev@bx.psu.edu
http://mail.bx.psu.edu/cgi-bin/mailman/listinfo/galaxy-dev
  