On 26.10.2011 16:13, Jeremy Goecks wrote: Hi Ross, I checked the following: wgetlink works, I can download the file. It's not saved asHistoryname.tar.gz but as export_archive?id=a69ee3e00cb4d02c. Anyway, I can unpack the archive with tar xfvz. hg head: Änderung:5955:949e4f5fa03a
Hi there, I'm in the middle of a decision: should I go into the cloud or not? I'm reading the docs on galaxy wiki, and I see that besides EC2, EBS I need S3 storage. What is that for (meaning: why galaxy needs S3)? @people already using it: how to you send NGS data? I need some feedback! :-)
It currently uses a tiny amount of S3 storage just to save configuration information about your instance. Long term though we plan to move dataset storage over to S3 as well. EBS has limits, S3 is more durable and scalable. Excerpts from Cittaro Davide's message of 2011-10-28 14:32:42 +: Hi
On Oct 28, 2011, at 5:35 PM, James Taylor wrote: It currently uses a tiny amount of S3 storage just to save configuration information about your instance. Ok.. never used AWS, actually, I didn't know S3 holds the information. I guess I will have to read some how-to Long term though we plan
On Fri, Oct 28, 2011 at 5:50 PM, Cittaro Davide cittaro.dav...@hsr.itwrote: On Oct 28, 2011, at 5:35 PM, James Taylor wrote: It currently uses a tiny amount of S3 storage just to save configuration information about your instance. Ok.. never used AWS, actually, I didn't know S3 holds the
Hello Oren, We use a sort of informal approach to implementing new Galaxy API features (they're implemented when the need arises), so unfortunately it doesn't look like the features you are looking for exist yet. If you'd like to contribute them, the community would certainly appreciate it!
The files are not touched - metadata is generated for the files, but the content of the files themselves is not changed. On Oct 28, 2011, at 3:21 PM, Oren Livne wrote: Dear Greg, Great, thanks! Just one more question: if I uncheck the copy data files option, does Galaxy change the original