RightAws support for attachment_fu #36
Closed
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…g 's', otherwise.
…sary on RightAws backend.
…e up of ISO-8859-1 characters.
|
Abandoning this, as we have moved off of attachment_fu. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Updated the :s3 backend to support use of RightAws for access to S3, alongside AWS::S3.
AWS::S3 is basically unmaintained now, whereas RightAws seems to be currently active.
If there's anything that I've done wrong or mucked up, I'd be happy to fix it -- thanks!
This is an updated pull request with a few more commits that help fix bugs and tweak the behaviour of the RightAws backend.