Unfortunately not, and with the migration of tools to the toolshed installation mechanism I don't imagine this will be addressed (at least by the team) anytime soon. If you wanted you could probably write a script that would reload a specified tool in each of the separate web processes, or just implement a complete rolling restart of your web processes to avoid service disruption while still loading the tool updates.
-Dannon
On Feb 6, 2013, at 8:40 PM, Anthonius deBoer <
thondeboer@me.com> wrote:
> I am indeed using multiple web processes and I guess I am talking about the "old" admine tool reloader...
> Is there any other way to do this for your own tools that you just manually place in tools etc.?
>
> Thon
>
> On Feb 05, 2013, at 06:22 PM, Dannon Baker <
dannonbaker@me.com> wrote:
>
>> Are you using multiple web processes, and are you referring to the old admin tool reloader or the toolshed reloading interface?
>>
>> -Dannon
>>
>> On Feb 5, 2013, at 9:13 PM, Anthonius deBoer <
thondeboer@me.com> wrote:
>>
>> > Hi,
>> >
>> > I find that reloading a tool's configuration file does not really work.
>> > First, you have to click the reload buttow twice to actually have it update the VERSION number (so it does read something)...
>> > But when I try to run my tool, the old bug is still there...
>> >
>> > I am using proxy server so something may still be cached, but I have to restart my server for it actually to pick up the changes...
>> >
>> > Any ideas?
>> >
>> > Thon
>> > ___________________________________________________________
>> > 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/ >>