Allow to upload images in development #52
Merged
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.
This is part 2 for the migration.
It allows a developer to upload her/his own covers to s3. This way we don't have to have a special image processing proxy in development and can benefit from the same production proxy (currently imagekit.io).
IAM user is specified as write-only and is scoped to /dev folder, so that an attacker can't use them to overwrite/delete production images:
See markevans/dragonfly-s3_data_store#30 (comment) on why s3:GetBucketLocation is needed.