Explain how to pass AWS configuration options
Prevent timeout errors when storing files

According to aws-ruby's maintainer upload timeouts typically occur
because the content length couldn't be determined directly. The fix is
fairly simple, just pass a path to the file instead of the file data and
the gem will open it in binary mode itself.

An integration test (and all of the support around that) had to be put
in place to maintain confidence about the test.
Document setting up for integration specs
Add ruby 2.0 to the travis build matrix
Code quality and gem version badges [ci-skip]
Release version 0.3.0, with history
Fix uploading, use alternate write syntax
Quick release of 0.3.1
Added support for asset_host
Merge pull request #5 from sborsje/master

Added support for asset hosts
Document using asset_host during configuration [ci-skip]
Include dependency status badge
Update dependencies, fix rspec deprecations
Update aws-sdk status to represent current version
Pass the file path, let aws handle reading

This attempts to mitigate timeout errors during upload. Reportedly they
are caused by incorrect content length reporting. By passing a path
rather than an actual IO object aws-sdk is forced to read in and stream
the file itself.
Secure env variables for integration spec
Patch release 0.3.2
add aws_read_options and aws_write_options
extracted uploader_read_options and uploader_write_options methods
Merge pull request #11 from sharespost/master

Add `aws_read_options` and `aws_write_options`