-
-
Notifications
You must be signed in to change notification settings - Fork 76
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
Issue with Heroku Cedar 16 #27
Comments
@benalavi Is there any chance you can fix this? I would really like to use this on Cedar 16. |
@whnunlife Did you manage to get it working on cedar 16 now? |
I have not had time to build this on cedar-16 yet, but if you just need to
use gm, possibly without the additional libraries compiled in, you can try
the apt buildpack and install gm via apt rather than this build.
The apt buildpack: https:/heroku/heroku-buildpack-apt
…On Wed, Apr 26, 2017 at 6:34 AM Stefan Trauth ***@***.***> wrote:
@whnunlife <https:/whnunlife> Did you manage to get it
working on cedar 16 now?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#27 (comment)>,
or mute the thread
<https:/notifications/unsubscribe-auth/AAAdMaF0H0leTGPE2SgUkRuPzV5QyOWnks5rz0f2gaJpZM4Mkt7H>
.
|
@benalavi I want to use this to work with parse-image on my parse server backend. I am not sure if it is enough to install gm via apt in this case. Do you know that? I will have a try... |
It works perfectly! And I think using apt to install the packages is also the better solution. This is what my
|
@funkenstrahlen No, the only solve for our project was to downgrade to cedar 14. |
@whnunlife What problem do you see? Works perfectly for me. |
@funkenstrahlen I haven't tried, it's been 2 month and the site has already launched. All I can remember, is that when we started dev, we were on Cedar 14, during that time, Heroku upgraded to Cedar 16 and then our ffmpeg commands started failing: I do have a copy of the error from slack that was being reported:
|
@whnunlife Hey man I got the same problem as you, so I included
|
@arathael Thank you man! This solved my problem as well. |
I feel like the unlucky one. Even after trying the apt buildpack and copying the exact same Aptfile as above my node calls to GraphicsMagick through aheckmann/gm keep raising the same error:
Worth mentioning that it works as intended locally. I even tried switching to cedar-14, which gave me a different exception:
I'm opening a ticket on Heroku's support page, but if anyone has a clue of what can I try next it'd be appreciated. Build log
|
For me helps to add to
|
Thanks=) My gm had worked! |
Hi |
The Aptfile worked for me too. Thanks! |
I am using the above Aptfile with all the extra packages, and everything worked fine until recently. Now my app is barking that Anyone having any issues with it recently? Anything that changed on Heroku? When I ssh into the dyno it does appear gm is installed:
|
Seems to have been an issue with |
For those having issues running this on newer Heroku stacks, I was able to get it working on |
That worked for me on heroku 18. |
Just noticed that heroku upgraded our instance to cedar 16, and now all GM commands are failing:
error: Worker 12: Error: Command failed: gm: error while loading shared libraries: libjasper.so.1: cannot open shared object file: No such file or directory
Downgrading to cedar 14 then resolved the issue. Just a FYI.
The text was updated successfully, but these errors were encountered: