If there are problems with this method please do let us know so we can
look in to it.
Your thoughts about using the FTP upload as you describe should work
fine. Unfortunately it is not written so generically, so you'll need to
set an FTP server name in the appropriate option in the config file
despite not having one, which will be displayed in the help text on the
upload form. However, this server name is not verified in any way and
can be any string.
I'm trying to set up a directory using FTP Upload (without an FTP server :-))
as discussed above.
I added a test directory for the a user 'auser'
ftp_upload_dir = /data/galaxy/
ftp_upload_site = localhost
to the universe.ini
We are using LDAP, so I set up a test directory called
but having added a file in can't see anything in the FTP upload
section or the 'Files uploaded via FTP' section even when 'auser' is
Is there something else I need to do?
This should be it - are you certain the email in Galaxy exactly matches
the email used in the directory name (it's case-sensitive)?
may be a silly question, but are you running a new enough revision that
has the FTP Upload code?
I think so. Just to double check is there a definitive way I can tell? In
<param name="ftp_files" type="ftpfile" label="Files uploaded via FTP"/>
So I got this to work by hacking basic.py.
def visible( self ):
self.tool.app.config.ftp_upload_dir = '/data/galaxy'
self.tool.app.config.ftp_upload_site = 'localhost'
I can now see my files in my user directory. What is the best part of the code
to use log.warning() to see what's going on? How can tell if it is reading the
ini file ok?
My next question is based on permissions. It looks like galaxy has to own the
file (as nobody in your example) to upload and remove it from the directory.
I'd like to change it to be more forceful, which would allow galaxy to remove
the file if group owned by nobody. What module/lines do this and what impact
would such a change have?
Thanks for any help,
galaxy-dev mailing list