You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have a lambda function that processes MP3s. One of the files in my project is an FFMPEG binary which requires execute permissions so that my Node code can execute it. The binary has the needed permissions on my local computer, and everything works locally, but when I use node-lambda to deploy to AWS the permissions are lost (the binary ends up with just read permission) so it can't be executed. I'm able to work around the issue by zipping this project by hand and uploading the ZIP file to AWS the old fashioned way--the needed file permissions are preserved when I ZIP it by hand.
The text was updated successfully, but these errors were encountered:
@demian85
The ARAtlas problem looks like #333.
However, I thought that the problem of @demian85 is different from that.
Could you please tell us a little more?
@ARAtlas
Thank you for your reply.
If I had the same problem as #333, I think that the latest version has been solved, so can you try it?
(The latest is 0.11.3)
I have a lambda function that processes MP3s. One of the files in my project is an FFMPEG binary which requires execute permissions so that my Node code can execute it. The binary has the needed permissions on my local computer, and everything works locally, but when I use node-lambda to deploy to AWS the permissions are lost (the binary ends up with just read permission) so it can't be executed. I'm able to work around the issue by zipping this project by hand and uploading the ZIP file to AWS the old fashioned way--the needed file permissions are preserved when I ZIP it by hand.
The text was updated successfully, but these errors were encountered: