My bad, I should have been clearer. What I mean is that no one should be
able to access it unless I give explicit permission. Browsing or
installing tools shouldn't be possible either without permission.
Serrano
On 09/23/2013 02:54 PM, Greg Von Kuster wrote:
> It's a bit unclear what you mean by "private" here, but it's possible
> to at least force users to login to use a Tool Shed if you include the
> following setting in the [app:main] section your tool_shed_wsgi.ini file.
>
> # Force everyone to log in (disable anonymous access)
> require_login = True
>
> Greg Von Kuster
>
> On Sep 22, 2013, at 2:39 PM, Serrano Pereira
> mailto:serrano.pere...@gmail.com>> wrote:
>
>> Hello,
>>
>> Is it possible to make a Galaxy Tool Shed private? The only method I can
>> think of at this moment is to use Apache's configuration to restrict
>> access to certain IP addresses. I was wondering if there are alternative
>> methods.
>>
>> Regards,
>> Serrano
>> ___
>> 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/
>>
>> To search Galaxy mailing lists use the unified search at:
>> http://galaxyproject.org/search/mailinglists/
>
___
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/
To search Galaxy mailing lists use the unified search at:
http://galaxyproject.org/search/mailinglists/
