Open DieracDelta opened 3 years ago
If you're using a --host
other than the default, you'll need to pass that param to hyp daemon status
too
I've added --host
to both invocations. Same output:
❯ hyp --host hyperspace info
The daemon is not active. Please run:
hyp daemon start
❯ hyp --host hyperspace daemon status
Hyperspace v3.19.0
Hyperspace API v1.15.1
Your address: (Not Hole-punchable)
Ah, it looks like the hyp
CLI isn't respecting this config: https://github.com/hypercore-protocol/cli/blob/master/lib/hyper/index.js#L16 and https://github.com/hypercore-protocol/cli/blob/master/lib/commands/daemon/status.js#L20 (and a few other spots)
We should either add a CLI flag or an env var. Any thoughts on which?
cc @andrewosh @mafintosh
What would the CLI flag/env var be specifying? From a usability standpoint, either sounds fine on my end as a user.
I tried making some local modifications to this for testing and I would also mention that the hyperspace-mirroring-service
is also a daemon that needs to be running for the CLI to work. I've been trying for the last while to get that running in a Docker container and I can't make sense of it; its pretty ambiguous.
When I start hypercore with
hyperspace --storage $STORAGE --host $HOST --port $PORT
, then run:This is preventing me from using any of the
hyp
commands. Any advice? Bothhyp info
andhyp daemon start
connect to the daemon, as it prints out: