-
Notifications
You must be signed in to change notification settings - Fork 9
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
This gem is failing on environment without HOME (like AWS Lambda) #25
Comments
Great find, thanks for logging! |
We only use `Dir.home` in a couple of places, so it's not a bit deal to allow user_home to be overridden. This is now possible via the --user-home/-u [DIR] flag. [fixes #25]
I decided to solve this issue by giving you a new CLI flag — However, you can also add it to your |
* Refactor and changes to support custom user_home. We only use `Dir.home` in a couple of places, so it's not a bit deal to allow user_home to be overridden. This is now possible via the --user-home/-u [DIR] flag. [fixes #25] * Tweak to an example. * Support for AWS Lambda and envs without $HOME * Fixing flakey test
@kigster I think Lambda does not have user-home dir at all, so we can pass empty user home? |
@jpalumickas You can pass whatever you like, but it must be a valid directory. Honestly, this is ONLY used for |
I try to use this gem on AWS Lambda and I get this error. It's failing to get
Dir.home
The text was updated successfully, but these errors were encountered: