AWS S3, Paperclip missing required :bucket option

Question

I\'m trying to use Paperclip and SWS S3 on Heroku to let users upload images.

I do not have my credentials stored in a yml file. I\'ve followed the instructions on t

Answer 1

Do heroku config to check your environment variables.

Normally they are all caps and have underbars instead of spaces.

If it is not set, you should set the environment variable with

heroku config:add BUCKET_NAME=my_bucket_name

Update your code:

:bucket => ENV['BUCKET_NAME'],

Heroku reference

Answer 2

Scott, sorry if there was any confusion here.

I am the author of the Dev Center article. As B Seven stated above the AWS Config Vars need to be set on the Heroku application.

Heroku has recently updated their documentation (https://devcenter.heroku.com/articles/config-vars#example) and set is preferred over add going forward.

$ heroku config:set AWS_BUCKET=your_bucket_name
$ heroku config:set AWS_ACCESS_KEY_ID=your_access_key_id
$ heroku config:set AWS_SECRET_ACCESS_KEY=your_secret_access_key

Answer 3

• Insert into schema.rb table "instructors" this line

create_table "instructors" do |t|
    ...
    t.string   "bucket"
end

• Add to controller @instructor[:bucket] = ENV['S3_BUCKET_NAME']
• Run "rake db:setup"

Answer 4

I think you may have made the same mistake I did. In your production.rb file, do not edit the text to add your specific S3 keys. Just copy-paste the text directly as is listed in the tutorial.

#production.rb
config.paperclip_defaults = {
  :storage => :s3,
  :s3_credentials => {
    :bucket => ENV['AWS_BUCKET'],
    :access_key_id => ENV['AWS_ACCESS_KEY_ID'],
    :secret_access_key => ENV['AWS_SECRET_ACCESS_KEY']
  }
}

Then, set the environmental variables AWS_BUCKET, AWS_ACCESS_KEY_ID, and AWS_SECRET_ACCESS_KEY as described by the author of the dev center article.

Answer 5

Make sure you restart your CLI of choice when setting values with environment variables. Don't be like me and set up Paperclip and AWS correctly with ENV variables and then waste a bunch of time on Google only to fix the issue by quitting and reopening Terminal.