You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It seems that a lot of carrierwave_direct's logic is generating query parameters for direct S3 upload. However, the aws-sdk gem already has this functionality. Also, carrierwave_direct's logic is Rails/HTML-specific, while aws-sdk generates these parameters as a Ruby hash, so you can use it either to generate HTML fields or to return a JSON response. Maybe carrierwave_direct could just leverage aws-sdk for generating these presign parameters?
The text was updated successfully, but these errors were encountered:
janko
changed the title
What is the advantage of carrierwave_direct over aws-sdk?
Using aws-sdk to generate parameters for direct upload
Aug 11, 2016
It seems that a lot of carrierwave_direct's logic is generating query parameters for direct S3 upload. However, the aws-sdk gem already has this functionality. Also, carrierwave_direct's logic is Rails/HTML-specific, while aws-sdk generates these parameters as a Ruby hash, so you can use it either to generate HTML fields or to return a JSON response. Maybe carrierwave_direct could just leverage aws-sdk for generating these presign parameters?
The text was updated successfully, but these errors were encountered: