-
Notifications
You must be signed in to change notification settings - Fork 74
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
I am having an issue using it on heroku #10
Comments
It needs GCC and to compile stuff, I think you can't do that on Heroku. |
Now that I think of it, it could be an issue with writing to Do you know where you can write temporary files on Heroku? |
I tried writing a file to /tmp and it seemed to work fine. This file is used by Rack-based servers to start the application.require ::File.expand_path('../config/environment', FILE) GCC is also available on Heroku as well. I also saw this error message.... |
It looks like the process has been killed by a supervisor, it could have used too much processor or something like that, you should contact Heroku and ask for clarification. |
Have you got any experiences deploying it to another platform like AWS? |
No, sorry. |
Can you please let me know which platforms you had luck with? |
@henrylily120 Heroku will not let a request run longer than a 30 seconds. You can get around this by pushing your OCR task off a queue like Resque or SideKiq. I ran into a similar issue with running some AI code on Heroku. Feel free to ask any questions about how to use workers on Heroku. |
@henrylily120 How were you able to get it to run on Heroku? |
@leoromanovsky Heroku wont let you use tesseract on a web dyno. You will need to use tesseract in a worker dyno. |
@Eunoia Hey yep, I got that part and am ready to use Sidekiq. I'm actually having trouble and running into a compilation error during the deploy. Any guidance there? |
I sent you an email, lets remember to share the results here. |
@Eunoia and I chatted offline. We tried going back to ffi-inline version 1.9.0 without any luck. The take-away was to try and get my sidekiq workers running on EC2 instead of Heroku. |
It works just fine locally, but when I deployed it on heroku, it gave me this error. Any assistance is appreciated.
The text was updated successfully, but these errors were encountered: