ac692b04f4
* log: fix bugs expand coverage and optimise * log: fix linter issues * log: fix linter issue and pack methods in same file * log: drop defer * logger: move global check inside getfields and remove unused test function * logger: Increase note thanks @gloriouscode * logger: wrap error with writer type * logger: change variable name * logger: change variable names and remove validsublogger func as it doesn't add functionality over a standard map call * logs: error when unsupported output is applied on setup calls * logs: add glorious suggestion * logger: add protection to reduce olympic gold medal races * logger: fix linter issues * log: glorious niterinos
GoCryptoTrader Backtester: Database package
This database package is part of the GoCryptoTrader codebase.
This is still in active development
You can track ideas, planned features and what's in progress on this Trello board: https://trello.com/b/ZAhMhpOy/gocryptotrader.
Join our slack to discuss all things related to GoCryptoTrader! GoCryptoTrader Slack
Database package overview
This package is responsible for the loading of kline data via a user's existing GoCryptoTrader database. It can load existing data from the candles and trades tables.
For more information on the GoCryptoTrader database, read this readme.
Ensure that your database has data and has been seeded with exchanges. For more information on this, please see this readme.
Database credentials
Defaults
The default database will be loaded from your GoCryptoTrader config. See this for database configuration and implementation.
Overriding the GoCryptoTrader config
Database configuration details can be overridden in the .strat config file to allow other sources to be used and not rely on existing GoCryptoTrader configuration. See this readme for details on config customisation
Please click GoDocs chevron above to view current GoDoc information for this package
Contribution
Please feel free to submit any pull requests or suggest any desired features to be added.
When submitting a PR, please abide by our coding guidelines:
- Code must adhere to the official Go formatting guidelines (i.e. uses gofmt).
- Code must be documented adhering to the official Go commentary guidelines.
- Code must adhere to our coding style.
- Pull requests need to be based on and opened against the
masterbranch.
Donations
If this framework helped you in any way, or you would like to support the developers working on it, please donate Bitcoin to:
bc1qk0jareu4jytc0cfrhr5wgshsq8282awpavfahc