-
Notifications
You must be signed in to change notification settings - Fork 29
AWS Install? #6
Comments
imagemagick and gm are not nodejs packages but binaries. they need to be installed by the proper package manager. What are you using in AWS? elastic beanstalk? |
Yea using ElasticBeanstalk. I swear I saw them on npm.... Here's the error I get:
|
have a look there: http://docs.aws.amazon.com/elasticbeanstalk/latest/dg/customize-containers-ec2.html and here: http://docs.aws.amazon.com/elasticbeanstalk/latest/dg/ebextensions.html basically: create .ebextensions folder at the root of your project in parse-image.config:
deploy OR |
oh, you are saying to USE the binaries and not nodejs packages...gotya..will report back with proper EB config once I get it working |
not sure if your image use the AWS AMI or a debian, for sure it works with APT like described. never tested with yum. |
Yep i did that, I even added libpng and libjpeg because I thought that was what is causing the decode error
|
At what point is that error thrown? |
from what I can tell
yum logs on beanstalk say imagemagick and graphicsmagick installed successfully.
Code is working on parse.com. Haven't changed anything. |
@nitrag this is a reverse engineered version of the official one :) I'll dig deeper. |
Seems to be the same as #7 |
I was hoping that adding these three as dependencies would be all we need to do. Why doesn't just adding dependencies work?
The text was updated successfully, but these errors were encountered: