thoughtbot/paperclip — Issue #770: Thoughts on adding s3 gem as a storage option?
Author: jakepaul
Created: 2012-03-04 00:34:17+00:00
State: open

I've been using qoobaa's [s3 gem](https://github.com/qoobaa/s3) with Paperclip in two production apps for a long time and have found it to work quite well. Jakub (qoobaa) used to maintain an initializer that could be to override Paperclip's S3 class, but he removed it a few months ago, presumably because he doesn't need it himself anymore.

I originally started using the initializer after having problems with the ancient aws-s3 gem, and have come to prefer it to fog and aws-sdk if for no other reason than qoobaa's gem seems so much more lightweight. Here's a quick-and-dirty comparison of the relative size of these gems, including dependencies (I just ran `gem install` in an empty gemset on OS X):

* aws-sdk: 5.9MB
* fog: 9.3MB
* s3: 217kb

Both of the other gems obviously include interfaces to a bunch of other AWS services, which helps to explain their size. Anyway, the reason I bring this all up is to ask whether you'd be open to adding an option to use qoobaa's gem as a backend. I'd try to do most of the work, but I thought I might ask before I spend too much time on it, in case this has been considered before and decided against for whatever reason.