Locally runnable server with built-in data caching, providing both tick-level historical and consolidated real-time cryptocurrency market data via HTTP and WebSocket APIs
I propose a --proxy argument is added to the tardismachine.js binary, such that a proxy can be fed in independently of environment config etc. That argument can then be passed into the Options object of tardis-node.
As per https://github.com/tardis-dev/tardis-node/issues/32,
tardis-node
andtardis-machine
do not work when run behind a corporate proxy. This issue captures thetardis-machine
part of the problem.I propose a
--proxy
argument is added to thetardismachine.js
binary, such that a proxy can be fed in independently of environment config etc. That argument can then be passed into theOptions
object oftardis-node
.To that end, please see this PR which I think should make this all work: https://github.com/tardis-dev/tardis-machine/pull/5