-
-
Notifications
You must be signed in to change notification settings - Fork 1.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
dragonfly/s3/heroku #3397
Comments
Did you see this #3392 ? |
Is this fix on master, or do I need to specify 4-2-stable? |
This fix is also on |
Thanks @bricesanchez |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Feel free to close, but am I missing something obvious? I have done every step in the heroku setup, and I'm still not able to get the app to use s3 for image/file uploads. Heroku config vars are set correctly. I've tried forcing with
Refinery::Core.config.s3_backend = true
in production.rb.All uploads are going into ephemeral storage.
The only way the app will even attempt to write to s3 is if I uncomment the lines that set the datastore config in the images initializer, and change
config.s3_datastore = Refinery::Dragonfly.s3_datastore
toconfig.s3_datastore = true
, but then I get errors that the bucket_name hasn't been set on the S3DataStore (from deep in refinery-dragonfly)Also, the s3 guide mentions adding dragonfly config to the core initializer, but the core initializer now says that dragonfly has its own initializer, though there is no
initializers/refinery/dragonfly.rb
in the generated app.I'm using Ruby 2.4.3 and rails 5.1.6.
The text was updated successfully, but these errors were encountered: