mirror of https://github.com/d0zingcat/gocryptotrader.git synced 2026-05-13 23:16:45 +00:00

Files

Ryan O'Hara-Reid 81a8b4a575 common: remove SimpleTimeFormat const for time package layout const DateTime (#1246 )

* switch over to package defined const for time layout

* bump appveyor playa

* bumperino to latest while setting patherino

* whoooops

* bump VS version set GOROOT

* puge build cache

* Revert "puge build cache"

This reverts commit 315bb578afc19529457f435e52af2172f5143bc5.

* bumperino to test

* purge setting of golang directory for version and allow default

* purge cache state when file change

* whoops

* thrasher: nits

* don't need to flusherino the cacherino

---------

Co-authored-by: Ryan O'Hara-Reid <ryan.oharareid@thrasher.io>

2023-07-06 11:17:43 +10:00

main.go

common: remove SimpleTimeFormat const for time package layout const DateTime (#1246 )

2023-07-06 11:17:43 +10:00

README.md

backtester: standalone application (#988 )

2022-09-08 16:22:30 +10:00

README.md

GoCryptoTrader Backtester: Configbuilder package

This configbuilder 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

Configbuilder package overview

What does the config builder do?

The config builder runs you through the process of creating a strategy config (.strat) file. Configs can also be generated via test code under config_test.go. Once the config is created, when running the backtester, you can reference it via go run . -configpath=(path-to-strat-file)

How do I run it?

go run .

Anything else?

The config builder will ask you all the necessary questions required to create a config file. If there is anything confusing, feel free to ask a question in our Slack group or open an issue!

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 master branch.

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