Any more thought on how to accomplish this without my current hack? Ideally it would be great if this feature could become part of galaxy-central. This is a feature that we would really like to implement so that our reports can link to the output files.
Thanks, Ilya -----Original Message----- From: James Taylor [mailto:ja...@jamestaylor.org] Sent: Friday, October 21, 2011 9:47 AM To: Chorny, Ilya Cc: galaxy-dev@lists.bx.psu.edu Subject: RE: [galaxy-dev] FW: how do I pass the URL of the input and output files to my tool wrapper? Excerpts from Chorny, Ilya's message of 2011-10-21 01:51:03 +0000: > I get the following error from routes > > AttributeError: 'thread._local' object has no attribute 'mapper' Okay, what I suspected. This is a product of the fact that job running is decoupled from the web frontend. The job runner doesn't necessarily live in the same process or even on the same machine as the web interface. You could have multiple web interfaces serving different base urls feeding one job runner. I don't have any simple answer to this. You could try to initialize route's mapper in the job runner, but I think this would be a big mistake. Instead you probably want to capture the URL somehow when the job is created. I need to think about it some more. -- James Taylor, Assistant Professor, Biology / Computer Science, Emory University ___________________________________________________________ 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/
