Prepare for heroku-24 #2826
Open
Prepare for heroku-24 #2826
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
|
wiki updated with changes at https://sciencehistory.atlassian.net/wiki/spaces/HDC/pages/1915748368/Heroku+Operational+Components+Overview |
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.
Minor tweaks necessary for moving to heroku-24 (ref #2688 ), as well as doc improvement encountered.
All these changes are backwards compat, so can be merged into master and deployed on heroku-22 as well, no problem.
To switch to heroku-24:
heroku stacks-- wont' take effect until next deployhttps://github.com/brandoncc/heroku-buildpack-vipsfrom buildpacks, no longer necessaryheroku config:set TESSDATA_PREFIX="/app/.apt/usr/share/tesseract-ocr/5/tessdata/" -r productionNote there may be a brief period after deploy but before you set
TESSDATA_PREFIXwhere tesseract can't find non-English language modules. Shouldn't really be an issue.This has been tested on staging, with
heroku run "rspec system_env_spec"passing, plus a manual test of ingesting a TIFF and OCR'ing it. (Haven't manually tested everything, just that one, counting on tests!)