-
Notifications
You must be signed in to change notification settings - Fork 32
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
Deployment issue with associated libraries--- #11
Comments
what is your error? |
essentially, in production, a 502 gateway error is returned. It only happens when salient is installed. When i un-install, everything works fine. I re-install, nothing works. Are there any libraries along with salient that might be in conflict with aws deployment? @morenoh149 |
502 gateway is usually a misconfigured router in your infrastructure. Unless this project provides cloud formation or docker files this issue is beyond the scope of the project. I'm not sure why npm installing salient would misconfigure your gateway, that would be very surprising if true and you should try some sanity checks before making that conclusion. You should ask the amazon support forums about your specific production setup. |
That conclusion is highly correlated by installing and uninstalling the package. Actually, even aws sdks have issues due to dependencies which yours has many. Maybe you should update your library every now and then (last updates are several years old...) and make sure all dependencies conform to industry standards :). thanks! |
Its not my project. But maybe if you can narrow down the issue it can be fixed. |
Great library on my local but causes problems when deployed to AWS, and thus cannot be used in production. Really wanted to use it for the sentiment analysis, especially notice of sarcasm...
The text was updated successfully, but these errors were encountered: