Quote from: ewibit on July 11, 2013, 01:11:20 PM

Code:

ADVICE is to HOLD @ 85.810 (NaN)

which part of config.js do you need?

I just looked into this and Bitstamp has changed their API, Gekko asks for data in a format not supported anymore (old API, new API). This means that Gekko currently does not work on Bitstamp. I am looking into a fix and hope to resolve this ASAP.

Quote from: ewibit on July 11, 2013, 01:11:20 PM

(BTW: is there any possibility to git pull without to fill out config.js every time new? - I rename the existent to .bak and copy/paste the settings in the new one)

Well the main reason is that the config is not solid, the settings may change and using an old settings file can result in Gekko crashing. You could place the config somewhere else (or rename like you did) and make a small script with `node gekko config=config.js.bak` to force Gekko to use another file as config. You can read more about that here, though I would advice against this.

Quote from: jago25_98 on July 11, 2013, 06:29:36 PM

Any ideas?

Gekko has dependencies (like momentjs), you can install them by running `npm install` in Gekko's directory.