This repository has been archived by the owner on Jul 13, 2023. It is now read-only.
-
-
Notifications
You must be signed in to change notification settings - Fork 2.4k
S3 #2483
Comments
Also experiencing similar problems with this too. Upgrade AWS SDK 3.0.1 and now receive this message: NameError: uninitialized constant Aws::VERSION |
@jasonivers This should fix it #2481 - I guess for now you can freeze |
That's what I've done... Hopefully someone will merge that PR soon
…On Fri, Sep 8, 2017, 6:53 AM Wojciech Wnętrzak ***@***.***> wrote:
@jasonivers <https://github.com/jasonivers> This should fix it #2481
<#2481> - I guess for now you
can freeze aws-sdk to ~> 2.0
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#2483 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AARnudA-3Xn7-cQnoIqPb12_44MQpYV5ks5sgUbFgaJpZM4PNuqK>
.
|
Paperclip uses the Aws::VERSION to check features and compatibility of certin versions like 2, 2.0.33 and above 2.3.0. For now you can add the missing method VERSION in your paperclip initializer or any file that get loaded like the following: module Aws It worked for me but use it with caution and test to ensure that nothing breaks in your code. |
We have migrated to awk-sdk-s3. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Amazon has recently updated their SDK gems to version 3. This appears to have broken Paperclip's support of S3, as files are now being uploaded empty (0 bytes).
I don't have the time to dig through the gem to figure out where the issue is, exactly, at the moment, as I'm down 2 developers, but I would highly appreciate some help, or if there is a newer, more actively maintained repo (last real update was December of last year) that someone could point me at...
The text was updated successfully, but these errors were encountered: