[ckan-discuss] CKAN CSV alert

Rufus Pollock rufus.pollock at okfn.org
Tue Jun 8 20:06:59 BST 2010

On 8 June 2010 19:39, Tim McNamara <paperless at timmcnamara.co.nz> wrote:
> On 8 June 2010 04:01, Benoit Boissinot <bboissin at gmail.com> wrote:
>> On Mon, Jun 7, 2010 at 5:28 PM, David Read <david.read at okfn.org> wrote:
>> > Christos,
>> >
>> > One last thing: I've changed the file compression from gzip to zip, so
>> > that Windows machines can open these files more easily.
>> Can't the webserver be configured to use gzip instead of the app doing
>> it by itself?
> Yes, it can also smartly decide how to compress the data depending on which
> compression the agent accepts.
> I'm interested in why CKAN's implemented this behaviour itself.

CKAN does *not* implement this: the results of the dump command are
json or csv and the the command line scripts in use at the moment runs
those results through gzip:

paster db simple-dump-csv | gzip > output.csv.gz

The obvious reason for doing this is that the files are transported
around by e.g. scp and not just served direct off a webserver (though
even here we could just use rsync with -z option ...)


More information about the ckan-discuss mailing list