Re: [galaxy-dev] About Galaxy Configuration

2012-05-24 Thread Oleksandr Moskalenko

On May 23, 2012, at 11:42 PM, Ciara Ledero wrote:

 I didn't know that. Thanks for the reply! Now I have a new set of questions. 
 First, how do I list myself as an admin? Should I just literally add my login 
 detail in the config file? Second, my colleague would like to be able to edit 
 and view the changes that he has made in his tools, even if I am doing some 
 editing myself. Yesterday, he was running Galaxy and I was editing some 
 tools. Since he has already started the instance, I got a socket error 
 telling me that the address was already in use. Because of that, I was not 
 able to see my revisions. What can we do about this? We're currently 
 searching for ways on how Galaxy can handle 'multiusers'.
  
 Thanks again!

As it was already pointed out you don't have to restart the Galaxy instance 
once your tool has been loaded once. As long as you are in the administrators 
list (see the admin_users variable in the universe_wsgi.ini) you can open a 
separate browser tab for the 

http://YOUR_GALAXY_URL/admin/reload_tool?reload_tool_button=Reloadtool_id=TOOLID

URI and just reload that page any time  you need to refresh the wrapper you 
modified.

Regards,

Alex___
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/

Re: [galaxy-dev] About Galaxy Configuration

2012-05-24 Thread Ciara Ledero
Okay, we'll do that! Thanks for the help.
___
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/

Re: [galaxy-dev] About Galaxy Configuration

2012-05-23 Thread Ross
Hi, Ciara,

AFAIK new tools always require a server restart at present, but an
already loaded tool can have updates to the tool XML re-read using the
'Reload a tool's configuration' option from the administrative menu if
your login is listed as an administrator in the config file.

Restarting Galaxy seems relatively benign if jobs are running on a
cluster. SGE jobs (eg) will be correctly handled and managed. Busy
users may see a service unavailable message from Apache for the time
it takes to restart but in my experience they can generally cope with
the occasional unscheduled server bounce to import a new tool - YMMV


On Thu, May 24, 2012 at 1:10 PM, Ciara Ledero lede...@gmail.com wrote:
 Hi there,

 I understand that everytime I create a new tool, I would have to restart
 Galaxy to see the changes that I've made. But if somebody else has already
 started Galaxy on our server, I won't be able to see my newly developed
 tool. I would be able to access the site, yes, but I won't see my tool. Is
 there a way around this?

 Cheers,

 CL

___
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/


Re: [galaxy-dev] About Galaxy Configuration

2012-05-23 Thread Ciara Ledero
I didn't know that. Thanks for the reply! Now I have a new set of
questions. First, how do I list myself as an admin? Should I just literally
add my login detail in the config file? Second, my colleague would like to
be able to edit and view the changes that he has made in his tools, even if
I am doing some editing myself. Yesterday, he was running Galaxy and I was
editing some tools. Since he has already started the instance, I got a
socket error telling me that the address was already in use. Because of
that, I was not able to see my revisions. What can we do about this? We're
currently searching for ways on how Galaxy can handle 'multiusers'.

Thanks again!

On Thu, May 24, 2012 at 11:19 AM, Ross ross.laza...@gmail.com wrote:

 Hi, Ciara,

 AFAIK new tools always require a server restart at present, but an
 already loaded tool can have updates to the tool XML re-read using the
 'Reload a tool's configuration' option from the administrative menu if
 your login is listed as an administrator in the config file.

 Restarting Galaxy seems relatively benign if jobs are running on a
 cluster. SGE jobs (eg) will be correctly handled and managed. Busy
 users may see a service unavailable message from Apache for the time
 it takes to restart but in my experience they can generally cope with
 the occasional unscheduled server bounce to import a new tool - YMMV


 On Thu, May 24, 2012 at 1:10 PM, Ciara Ledero lede...@gmail.com wrote:
  Hi there,
 
  I understand that everytime I create a new tool, I would have to restart
  Galaxy to see the changes that I've made. But if somebody else has
 already
  started Galaxy on our server, I won't be able to see my newly developed
  tool. I would be able to access the site, yes, but I won't see my tool.
 Is
  there a way around this?
 
  Cheers,
 
  CL
 

___
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/