Files
gocryptotrader/communications
Ryan O'Hara-Reid e2d57540a6 Config overwrite bugfix (#363)
* Fix bug where on parsing an alternate new config it will overwrite main config.json in gct dir

* Stop movement of config.json file from root dir when a new config is parsed in

* Stop overiding config.json at gct dir with new config.json from root directory

* RM LN :D

* Fix bug where promptforconfig in config_encryption.go overwrites default config
Ensure periphery command packages do not interact or save over configuration
Ensure tests to not save over or change current testdata/config
2019-09-27 16:03:41 +10:00
..
2019-09-24 17:05:58 +10:00
2019-09-27 16:03:41 +10:00
2019-09-27 16:03:41 +10:00
2019-09-27 16:03:41 +10:00
2019-09-24 17:01:32 +10:00

GoCryptoTrader package Comms

Build Status Software License GoDoc Coverage Status Go Report Card

This comms package is part of the GoCryptoTrader codebase.

This is still in active development

You can track ideas, planned features and what's in progresss on this Trello board: https://trello.com/b/ZAhMhpOy/gocryptotrader.

Join our slack to discuss all things related to GoCryptoTrader! GoCryptoTrader Slack

Communications package

What is the Communications package?

  • This package allows for the communication of events/data that occurs in the to be exported out to a defined communication medium

Current Features

  • Slack bot support
  • SMSGlobal instant bulk messaging
  • SMTP messaging
  • Telegram bot support

How to enable example

  • In your config.json enable each individual communications package you desire
  • Please view the individual readme documentation inside the specific package for more details

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:

1F5zVDgNjorJ51oGebSvNCrSAHpwGkUdDB