Hi Daniel,
On 22 March 2012 08:20, Daniel Sobral <dsob...@igc.gulbenkian.pt> wrote:
> Hello,
>
> At the moment I don't think there is a way to restrict usage of specific
> tool(s) to specific user(s).
> Is anyone thinking on developing this kind of functionality?
> I guess it might be a bit complicated to implement?
>
> I guess an "easier" alternative is to have different galaxy instances
> running, each one with a different tool set?
>
>
Instead of running multiple instances I would recommend you to add few
lines of code in your tool configuration file (.xml)
1. Export the $__user_email__ variable along with the tool call section in
XML file.
ex:
<command>/path-to-tool/wrapper.sh ARG1 ARG2 ... $__user_email__
</command>
2. In the wrapper.sh script, add the following line in the before calling
your main program.
if [ "${@: -1}" != "vipin...@gmail.com" ];
then
echo 'You donot have enough privilege to access this tool, please
contact gal...@tuebingen.mpg.de'
exit
fi
By doing this way the tool name will be listed in the tool panel of Galaxy
instance, but for this specified
user can only access the same. I know this is not an automated way of
implementation and happy to hear
if somebody have another fix for the same.
I implemented this in my public Galaxy instance and it is accessible
here<http://galaxy.fml.mpg.de/tool_runner?tool_id=rquant_web>
.
HTH, Vipin
Thanks,
> Daniel
> ___________________________________________________________
> 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/
>
___________________________________________________________
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/
