-
Notifications
You must be signed in to change notification settings - Fork 998
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
Libv8 error when deploying errbit to heroku #1494
Comments
Thanks for the report. I have to admit here that Errbit has fallen pretty far behind in the heroku deployment area and that's probably going to continue to be the state of things unless someone picks up the torch. It is possible that it could be easier to use the docker container to deploy to heroku now because of the self-contained nature of containers. I'm going to mark this issue 'help wanted' in case anyone out there can help. |
Thanks for your response, appreciate it. |
I recently upgraded our errbit host from Ubuntu 18.04 to 20.04 after which I couldn't build libv8 anymore (good I still had it compiled). It's probably related to this version of v8 being quite a bit out of date. I have hardly checked but I suppose we only use it for asset compilation (with therubyracer)? In other projects we switched to mini_racer as therubyracer is dead (last release 2017). I just tried replacing therubyracer with mini_racer and so far it seems to work just fine (but I have no clue about Heroku). Just be aware that you probably have to use bundler < 2.2 due to a bug. If it weren't for things I personally don't like (like haml and mongo) I would probably invest some time to give errbit a refresh. Maybe I still do but currently it does the job for us quite well. This could also be a potential solution for #1492 |
Hey, thanks for your reply. Actually, advice from 2called-chaos helped me to get it working on Heroku. So actually I've changed the |
I managed to deploy it with Docker. I just had to create the following
|
@simon0191 great, but I think errbit should be able to run on Heroku without Docker. Hopefully mini_racer will solve this. |
Can someone test with current master? I'm not really in the Heroku game but I guess it should work. With Bundler 2.2 we might need to add another platform to the lock file (not quite sure what they use for a system stack) |
FWIW, I just tried to deploy with the current master and it failed using bundler 2.2. Downgraded to bundler 2.1.4 using the build pack 'https://github.com/heroku/heroku-buildpack-ruby.git#v219', with ruby 2.5.1 for Heroku-18 stack and rails 4.2.10 and managed to get through to the full deploy. |
Step 3: Describe the problem:
Steps to reproduce:
https://github.com/errbit/errbit/blob/master/docs/deployment/heroku.md
Deploy to Heroku
button provided in the guide:https://heroku.com/deploy?template=https://github.com/errbit/errbit/tree/master
Create App
Heroku form.Deploy App
Observed Results:
I've got an error during the bundle, I won't paste the whole stack trace because it's thousands of lines, so I will only paste bundle output and where it fails.
Expected Results:
I am not sure what's wrong here, I've changed the ruby version from the default 2.5.1 to the 2.7.2 but I've tried to bundle it on my local machine and it seems that bundle finished without errors for ruby 2.7.2.
Also, I was wondering if someone has tried to deploy Errbit to Heroku using the Heroku-20 stack.
The text was updated successfully, but these errors were encountered: