Jan van der Pas
2013-Apr-18 23:17 UTC
Missing :bucket option (S3), while it is defined in production initializers.
I got my S3 credentials defined in my production.rb, linkwise to this heroku post <https://devcenter.heroku.com/articles/paperclip-s3>. However when I''m testing it on Heroku, I get this error in my logs: "ArgumentError (missing required :bucket option)". What could be wrong? -- You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group. To unsubscribe from this group and stop receiving emails from it, send an email to rubyonrails-talk+unsubscribe-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org To post to this group, send email to rubyonrails-talk-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org To view this discussion on the web visit https://groups.google.com/d/msg/rubyonrails-talk/-/iTYd57TUco4J. For more options, visit https://groups.google.com/groups/opt_out.
tamouse mailing lists
2013-Apr-20 10:10 UTC
Re: Missing :bucket option (S3), while it is defined in production initializers.
On Apr 19, 2013 2:26 AM, "Jan van der Pas" <janvanderpas-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> wrote:> > I got my S3 credentials defined in my production.rb, linkwise to thisheroku post. However when I''m testing it on Heroku, I get this error in my logs: "ArgumentError (missing required :bucket option)". What could be wrong?>with the complete lack of code, very hard to help. do you test s3 storage is working prio to production? my guess: you are missing the s3 bucket to save to. -- You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group. To unsubscribe from this group and stop receiving emails from it, send an email to rubyonrails-talk+unsubscribe-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org To post to this group, send email to rubyonrails-talk-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org For more options, visit https://groups.google.com/groups/opt_out.
Seemingly Similar Threads
- [LLVMdev] [LNT] running LNT in 'the cloud'
- Fatal error: The remote end hung up unexpectedly
- cache-busting non-digest assets in sprockets in development a good idea? should headers in sprockets be configurable?
- No javascript runtime on Heroku
- Can't push to Heroku