Hello all,

Re: BitBucket Issue 538 - Admin action to reload ".loc" files without
restarting Galaxy

Currently Galaxy administrators can reload a tool's XML configuration
file, which is very helpful (especially as a developer working on
changes to a single tool). Similarly it would be useful to be able to
reload one (or all) of the *.loc files (e.g. if a new BLAST database
is added), without having to restart Galaxy.

Further to this, it would be useful to trigger this from a script via
the Galaxy API or otherwise. Should this be filed as a new issue, or a
comment on the existing issue?

Another idea for enhancement would be to monitor the loc files for
*automatic* reloading without user or script intervention (but that
might be too much magic), or simply (re)loading loc files on demand
rather than at startup.

Do the Galaxy team have any plans in this area?


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:


Reply via email to