Big Files Go Straight To S3 #631
Merged
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
…to s3. then create an external file in fcrepo, keeping the data consistant and making sure hyrax uses the right file all the time
alishaevn
approved these changes
Jun 18, 2024
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.
instead of uploading large files through fcrepo, upload them straight to s3. then create an external file in fcrepo, keeping the data consistent and making sure hyrax uses the right file all the time. This allows the files to be streamed to S3 and to still be represented in fcrepo in some way. They can also be direct downloaded from S3 and will work in serverless-iiif (but you don't really want to serve something that big from serverless-iiif)