Closed unRob closed 6 years ago
Good catch, this needs a rewrite, it's been a few years since I've touched it and my skillset has gotten better.
I'll go ahead and work on this one here in the next few weeks.
I'm having the same issue. The problem is that upstart, systemd, etc, don't set the HOME
environment variable, so calls to Dir.home
raise an error.
env -i ruby -e Dir.home
-e:1:in `home': couldn't find HOME environment -- expanding `~' (ArgumentError)
from -e:1:in `<main>'
The error comes from require 'bini/config'
, which immediately calls Dir.home
Gonna close this, as I'm rewriting the code currently. Won't include bini so it won't be an issue.
When v1.0.4 requires
bini
within an Upstart script, the following error appears:Here's how to replicate the issue:
Just thought someone might find themselves in the same situation, the easy fix is to add
env HOME=/
to the script, but this seems more like a hack.Also, great work, thanks!