Split config for multi bot scenarios

[chevdor]

I would like to make a proposal that can be discussed an probably kepts warm for later.

In case the user wants to run several instances, it would be to split the config into: 1- a main config file containing the common parameters (email for the alert, etc..) 2- a part dedicated to the method and options trading

Splitting the config does not have to be physical into N files, although this would have some benefits.

We could use profiles into the config file. Although, the ability to have trading params in a separat file would be sweet to exchange with other while not sharing confidential data such as the API Keys.

The config based on profiles could look like:

// Common section
// emails, etc...
recipient = bob@megacorp.com

// Default settings
sendEmails = true // for instance

// Profile#1: ema_10_21
profile = {name: 'ema_10_21', default: true}
// no need to define sendEmails as we like the default = true. See above
method = ema

// Profile#2: stop_loss
profile = {name: 'stop_loss'}
sendEmails = false // here we override the default value we defined
method = stop_loss

This would also allow starting the bot with a given profile depending on the current market mood as:

node gekko safety_first

It would also become handy to have 2 bots working conccurently:

node gekko ema_10_21
node gekko stop_loss

See also #110 and #132. Those issue may be probeblatic.

[askmike]

Currently users can use the config parameter to specify another config file. Multiple instances on different markets work fine, though multiple traders on the same market currently poses some problems (unless you use different history folders for each):

A stop loss as well as an EMA trading method will not be wise, because you either listen to watching trends or you don't. If you would run both those two advices they would not only speak against each other, but you are also paying double fees for all the extra positions to take (CEX.io is the exception here). In the future we might do something more advanced in the lines of multiple indicators combining advice but for now (as we only have two trading methods) this is way overkill.

---

I already have plans for people wanting to papertest or backtest using different methods / parameters: Gekko is going to support multiple markets & multiple traders. Currently actors are hooked up to the emitter they want to receive intel from directly, but I want to move this to a system where each market and each trader have their own feed. Than you can do these things in a single instance:

• Watch Bitstamp, trade for real 60min EMA 21/10, mail on trade, also do paper trading on 30min EMA 10/8, hook ircbot to the paper trader.
• Watch BTC-e, paper trade on every market and log best market for specific trading method / parameters.
• etc. etc.

Also the configuration is going to move to a webbased interface (optionally, but opt out).

[askmike]

• If you have an implementation thought out on how to deal with multiple methods (of which we only have two which are extremely similar) you can submit a pull request.
• If you want to separate the private information from the other settings you can also submit a pull as this will increase security.

But right now I don't want to spend to much resources on this, so for now I am closing this.

[askmike]

Awesome update: It was surprisingly easy to hook up redis pubsub to Gekko. This means that clusters of different configuration become a breeze. The only thing left is to create a new Market object that instead of a fetcher subscribes to redis pubsub. Here more info:

https://github.com/askmike/gekko/blob/localDB/docs/internals/Actors.md#redis-beacon