-
Notifications
You must be signed in to change notification settings - Fork 75
Open
Description
I was writing an automated script, which starts the Yeti server up again, if it's not running.
I did so because it was crashing quite often when I tried it on a local VM (see #91).
I was calling /bin/bash -c 'export HOME=/tmp; while true; do yeti --server; sleep 30; done' but the start of the Yeti server always resulted in the following crash:
Yeti v0.2.29 (Node.js v0.10.25) Error: TypeError: Arguments to path.join must be strings
at path.js:360:15
at Array.filter (native)
at Object.exports.join (path.js:358:36)
at Configuration.configurationFinder [as locate] (/usr/local/lib/node_modules/yeti/lib/cli/configuration.js:52:40)
at Configuration.proto.importFromDirectory (/usr/local/lib/node_modules/yeti/lib/cli/configuration.js:184:37)
at Configuration.proto.home (/usr/local/lib/node_modules/yeti/lib/cli/configuration.js:221:10)
at CLI.route (/usr/local/lib/node_modules/yeti/lib/cli/index.js:581:55)
at Object.<anonymous> (/usr/local/lib/node_modules/yeti/cli.js:16:10)
at Module._compile (module.js:456:26)
at Object.Module._extensions..js (module.js:474:10)
Report this bug at https://github.com/yui/yeti/issues
As reported in #36 my problem was solved by setting HOME to an existing path.
With /bin/bash -c 'export HOME=/tmp; while true; do yeti --server; sleep 30; done' it's now working, but it's not really clear that one needs to do so. Maybe a default would be useful?
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
No labels