James Casbon wrote:
On 5 February 2010 13:24, Pieter Neerincx email@example.com wrote:
Can someone help me understand the automagic (un)zipping in Galaxy?
In my universe_wsgi.ini there an option to enable gzip compression like this:
# ---- HTTP gzip compression ---- # If planning to run Galaxy as a production service, we recommend running Galaxy # through a proxy and enabling gzip compression there (instructions at # http://bitbucket.org/galaxy/galaxy-central/wiki/Config/ProductionServer )
This means you should use something such as mod deflate: http://httpd.apache.org/docs/2.0/mod/mod_deflate.html
I've also added the missing information to the wiki:
- Can I make automagic unzipping also work for *.zip files? Personally I prefer gzip, but many people in our lab are more familiar with things like winzip....
This is handled transparently by negotiation between the browser and the server. Your end user does not have to do anything - the browser unzips before rendering.
It may help to clarify that this only refers to compression of data sent from Apache to the client, so it does not include uploads or any data handling by Galaxy itself.
In response to one of the original questions, we chose not to allow uploading zip files since they can contain multiple files and upload is only designed to handle one file at a time. gzip is not a file container, so it is always guaranteed to contain one file (even if that file is a tar archive).
However, detecting the contents of a zip is simple, and we could simply reject any zips with > 1 file. So if people would find this to be useful, it's something we could add to our enhancements wishlist.
hope this helps, James _______________________________________________ galaxy-user mailing list firstname.lastname@example.org http://lists.bx.psu.edu/listinfo/galaxy-user