Skip to content
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

Not returning the correct app path on AWS Lambda #23

Closed
motocombotag opened this issue Mar 29, 2018 · 4 comments
Closed

Not returning the correct app path on AWS Lambda #23

motocombotag opened this issue Mar 29, 2018 · 4 comments

Comments

@motocombotag
Copy link

Fix it please. It wasted 2 days of my time.

@inxilpro
Copy link
Owner

Hm. I can try to help, but you’re going to need to provide a little more detail, and maybe try asking in a less entitled way. No one forced you to use my free, open source library. Most open source maintainers would probably just close an issue like this without any response.

@motocombotag
Copy link
Author

You're right. I apologize. I was that much frustrated. I didn't use your library directly - it was used by phantomjs which I used in a project and after some time-wasting, I realized that the path that is logged on AWS Lambda is /var/runtime/awslambda or something like that, while the actual Lambda function runs in /var/task.

@jrtipton
Copy link
Contributor

jrtipton commented Apr 30, 2018

  if (process.env.LAMBDA_TASK_ROOT && process.env.AWS_EXECUTION_ENV) {
    return process.env.LAMBDA_TASK_ROOT;
  }

...is one way to fix it

@inxilpro
Copy link
Owner

Fixed by #24

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants