Add ocr-languages bucket to intiialize minio command - #462
Merged
Conversation
dnass
approved these changes
Sep 3, 2026
dnass
left a comment
dnass
left a comment
Contributor
There was a problem hiding this comment.
Ran into this issue when I was setting it up locally this week. The fix looks good.
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
I was setting up a new local dev environment as I reinstalled the operating system on my computer last week and when I went to run step 14 I received a failure because the ocr-languages bucket didn't exist. I think in my last environment I set it up manually and forgot to add this in the minio script. This adds that bucket to be created in the initialize minio command step, so that it is available for putting the OCR data in that bucket in step 14.