Thanks Dan. The revision of Galaxy is the problem - the instance of Galaxy
on the cloud is a month old now; it is at revision 5064 so.
I'll release an update in the coming days along with an updated CloudMan.
Enis
On Mon, Mar 14, 2011 at 11:24 PM, Daniel Blankenberg wrote:
> Hi Karl,
>
> Using
Hi Karl,
Using the upload tool for https URLs was added in changeset 5220:425076fe5ea0.
I am not sure when this will make it to the Cloud image, but meanwhile, if you
can access the file without using ssl (just 'http'), you should be able to
upload. If this is not the issue you are experiencing
I changed the permission for the files to public (everyone can
open/download), but this did not fix the problem.
Also, to answer Dannon's question, I am entering the full path for these
files, eg. https://s3.amazonaws.com/bucketname/xyz.txt
>From the screencasts I have watched, I noticed that fa
Ah, permissions, that may be the ticket. I will try again and see.
thanks a lot!
karl
> Hi Karl,
> As a quick check, are the permissions for the S3 file set so anyone can
> read
> the file? That's required before Galaxy's upload tool will be able to
> access
> the file.
> Alternatively, if yo
Karl,
For the URL you're pasting, is it the full path to a file in your s3 bucket,
including the protocol (http://) ? For galaxy to recognize that it needs to
pull from a URL rather than the contents of the box, you need to use the full
string.
-Dannon
On Mar 14, 2011, at 4:40 PM, karlerh...
Hi Karl,
As a quick check, are the permissions for the S3 file set so anyone can read
the file? That's required before Galaxy's upload tool will be able to access
the file.
Alternatively, if you don't want to set such loose permissions, you should
be able to get a a signed URL for the given file us
6 matches
Mail list logo
