BITTREX_API_KEY and BITTREX_API_SECRET in your path
Provided I am logged in to Bittrex and have those two informations - what is the newbi way of "including it" in the path?
Docker-Compose Build
Works smooth, gives these NPM warnings, guess its because it's not yet NPM listed?
Docker-Compose Up
It executes, throw however these node-pre-gyp, tulind.cpp and NPM related warnings:
Running tests
Works smooth
General: Difference between "Production, Developing, Testing"
I get a bit lost here, I succesfully run Production, but dont know exactly what to do next. A few comments/questions:
I assume if I had actually managed to include the "BITTREX" path it would now have been running a selected strategy - how can I veriify which strategy that would be using?
As a noob I am not exactly sure what the difference is between prod, testing, develop. Would it make sense to distinguish this into three sections with more info, in regards to "testing the bot", "running the bot in production" & "Developing on the bot", I assume these three have different potential target users?
Gitclone / cd c core
All works smooth
Docker setup and installation
All works smooth
Running the bot live against bittrex
It says:
BITTREX_API_KEY and BITTREX_API_SECRET in your path
Provided I am logged in to Bittrex and have those two informations - what is the newbi way of "including it" in the path?
Docker-Compose Build
Works smooth, gives these NPM warnings, guess its because it's not yet NPM listed?
Docker-Compose Up
It executes, throw however these node-pre-gyp, tulind.cpp and NPM related warnings:
Running tests
Works smooth
General: Difference between "Production, Developing, Testing"
I get a bit lost here, I succesfully run Production, but dont know exactly what to do next. A few comments/questions:
I assume if I had actually managed to include the "BITTREX" path it would now have been running a selected strategy - how can I veriify which strategy that would be using?
As a noob I am not exactly sure what the difference is between prod, testing, develop. Would it make sense to distinguish this into three sections with more info, in regards to "testing the bot", "running the bot in production" & "Developing on the bot", I assume these three have different potential target users?
Backtesting via webinterface, terminal and editor
Configuring the Project
It states:
go to the config file in src/config/index.js and change the variables.
I assume this is here you would change strategies? How do I 1) pick a new strategy or 2) submit my own strategy?
What other variables would we expect developers would change here?