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
First of all, this gem is amazing and thanks for making it. Second, bitcast.io is sweet, we never knew about it.
Issue:
Is it possible to set different AWS credentials for each user, instead of hard coding into "aws.yml"?
Details:
We let users upload files to an S3 bucket they specify, using their own AWS credentials that we encrypt & store in a model. From the s3_multipart readme.md, we have to hardcode AWS credentials in "aws.yml".
The text was updated successfully, but these errors were encountered:
Looking through your code, if we can pass in our own s3_access_key and s3_identity to calculate_authorization_hash(), this would simply overwrite Config.instance.s3_access_key on Ln 101, 103, 105.
Then this gem could be used for applications that let people upload to their own S3 buckets or many S3 buckets, instead of just apps with a single bucket.
First of all, this gem is amazing and thanks for making it. Second, bitcast.io is sweet, we never knew about it.
Issue:
Is it possible to set different AWS credentials for each user, instead of hard coding into "aws.yml"?
Details:
We let users upload files to an S3 bucket they specify, using their own AWS credentials that we encrypt & store in a model. From the s3_multipart readme.md, we have to hardcode AWS credentials in "aws.yml".
The text was updated successfully, but these errors were encountered: