I also had this problem. Specifying gems in a specific order seems to work for some people:
config.gem "aws-s3", :lib => "aws/s3", :version => '>= 0.6.2' config.gem "paperclip", :version => '>= 2.3.1.1'
In my application, I also had a plugin (backup_fu) indicating right_aws , and I also had to comment out a line in my plugin:
# backup_fu.rb require 'yaml' require 'active_support' require 'mime/types' require 'right_aws' unless defined?(RightAws) require 'erb' class BackupFuConfigError < StandardError; end class S3ConnectError < StandardError; end class BackupFu
Does anyone know why this is a problem?
EDIT: In my application, I no longer require rights to everything, and then in the backup_fu file I changed the require line to require only right_aws if it is not already loaded. I found that by requiring a gem in environment.rb, it caused a conflict with the aws-s3 gem. So, now the backup_fu plugin will load it if necessary (usually only when starting as a rake task), but not when starting the application.
mysmallidea
source share