Thanks for your answer, and for pointing me to the right mailing list.
My tool actually feeds data libraries. It works in a similar way as the
"Copy data into Galaxy? No" functionality, in the sense that it creates
symbolic links rather than duplicating files, but it also provides an
interface to browse and select files in a finer way.
So my tool is already functional and my only problem is that the tomcat
user cannot create symlinks in folders created by Galaxy, because it
doesn't give write permissions to the group. I could do something like
a chmod 775 in a daemon, but I would rather avoid that.
Can anyone help me further?
Le 10/04/2012 04:39, Jennifer Jackson a écrit :
I am going to forward your question over to the galaxy-...@bx.psu.edu
mailing list so that it can get more visibility in the development
community. That list is probably where you will want to post regarding
similar topics in the future:
To get things started, I am wondering if you are asking about datasets
in histories or data in libraries? Parts of your question seem to
refer to both, or I have misunderstood (my apologies!).
If about data in libraries, then you can get around this by not
actually moving the data into the Galaxy directory structure at all,
and instead just link in data from some other location on the
filesystem (where you can control the permissions). See the "Copy data
into Galaxy? No" option described on this wiki:
Other data/lib/security related links, mostly admin UI:
http://wiki.g2.bx.psu.edu/Admin/Data Libraries/Library Security
Hopefully this helps or some more discussion on the galaxy-dev list
about your question will find a solution,
On 4/6/12 2:42 AM, Guilhem Sempéré wrote:
I would like folders created by Galaxy under the location defined by the
"file_path" parameter (which defaults to database/files) to be created
with permissions 775 instead of 755. Is this possible?
The reason for me asking this question is that I have developed an
external tool (running under Tomcat) for feeding Galaxy libraries. And
my tomcat user needs to be allowed to write to the mentioned folders.
The Galaxy User list should be used for the discussion of
Galaxy analysis and other features on the public server
at usegalaxy.org. Please keep all replies on the list by
using "reply all" in your mail client. For discussion of
local Galaxy instances and the Galaxy source code, please
use the Galaxy Development list:
To manage your subscriptions to this and other Galaxy lists,
please use the interface at:
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: