Yeah, there is not currently a great solution to this problem. Some have implemented a tools just like David's. You could also get around setuid with sudo, although the security implications are probably the same. I think the ideal system would be to start Galaxy as root, drop privileges, and then only regain them as necessary for these operations. --nate On Jan 30, 2012, at 9:31 AM, David Hoover wrote:

I'd love to know answers to this question as well. So far, all I've done is create two tools for copying files between Galaxy and a user's personal directories using a rather dangerous setuid executable.

I have mulled over two possibilities for this problem. One is to run Galaxy as root. The other is for each user to kick off their own personal instance of Galaxy as themselves, but accessing the same main database and file repository. The latter would require all files be read-write accesible to all users. Neither is good.

On Jan 30, 2012, at 4:29 AM, Sarah Maman wrote:

...

Dear all,

There is currently no link between an user ssh connection on his own account (own space on Unix) and the Galaxy connection. How to run Galaxy on an Unix user account? How to link the data storage system and the Unix user account (symlink?)?

The goal is to not need to copy or move data.

PS : Thanks a lot to David, Gordon, Brad, Christophe and Nate for your help on LDAP authentification. I always try to find a solution (Apache configuration). I will inform Galaxy list when I will find a solution.

Thanks in advance,

Sarah