Skip to content
forked from thoward/s3gzip

Read and write gziped content in S3 without hitting disk.

License

Notifications You must be signed in to change notification settings

kongregate/s3gzip

 
 

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 

History

3 Commits
 
 
 
 
 
 
 
 
 
 
 
 
 
 

Repository files navigation

s3gzip

Read and write gziped content in S3 without hitting disk.

Example

require 's3gzip'

id='S3_ACCESS_KEY_ID'
secret='S3_SECRET_ACCESS_KEY'

bucket='MY_BUCKET'
filename='a/folder/with/filename.gz'

S3Gzip::Writer.open(id, secret, bucket, filename) do |writer|
  writer.write 'some content, gzipped, then stored in s3.'
end

result = S3Gzip::Reader.read(id, secret, bucket, filename)

puts result
# Output:
# some content, gzipped, then stored in s3.

Methods

You can use S3Gzip::Writer in a variety of ways from a one-liner to many-liner. These three examples do the same thing:

require 's3gzip'

id = 'S3_ACCESS_KEY_ID'
secret = 'S3_SECRET_ACCESS_KEY'

bucket = 'MY_BUCKET'
filename = 'a/folder/with/filename.gz'
content = 'some content, gzipped, then stored in s3.'

writer = S3Gzip::Writer.new(id, secret, bucket, filename)
writer.write content
writer.close_and_send

S3Gzip::Writer.open(id, secret, bucket, filename) do |writer|
  writer.write content
end

S3Gzip::Writer.write(id, secret, bucket, filename, content)

When using the first method, close_and_send must be called. This is done automatically when using open or write class methods.

Also, please note that every time you write to the file on S3, it will overwrite the previous value. This is generally true with S3, but can be a bit confusing given S3's eventual consistency model. Read more about that in the AWS S3 FAQ.

Requirements/Dependencies

Copyright

Copyright © 2014 Troy Howard. See LICENSE for details.

About

Read and write gziped content in S3 without hitting disk.

Resources

License

Stars

Watchers

Forks

Releases

No releases published

Packages

No packages published