Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Spike: add OPM_THREAD_LIMIT to iiif_print instead of each individual project #196

Open
ShanaLMoore opened this issue Mar 21, 2023 · 0 comments

Comments

@ShanaLMoore
Copy link
Contributor

ShanaLMoore commented Mar 21, 2023

Summary

To speed up the process of OCR, we've been setting an env var for each individual project.

Kirk noticed that ESSI has it defined when they call tesseract and thought it'd be nice if we did the same in iiif_print, to remove the step of adding it to each project's yml/rancher.

This ticket is to evaluate if using it inline works, and determine if we should proceed with including it in the iiif_print gem.

Acceptance Criteria

  • [ ]

Screenshots or Video

Testing Instructions

Notes

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant