fix: refactor tradingview

[chrisleekr]

Description

The TradingView container was developed with a very simple python web server.
However, it was found that TradingView container was causing some issues with some scenarios.

• When a symbol is not supported by TradingView
• When requests were taking a long time.

To resolve the issue, this PR has refactored TradingView container with Flask.

How to test:

$ git pull
$ git checkout fix/refactor-tradingview
$ npm run docker:build
$ docker-compose -f docker-compose.server.yml up -d
$ docker ps -a
$ docker logs binance-bot -f --tail=1000 | bunyan

Related Issue

#368 #381

Motivation and Context

How Has This Been Tested?

Screenshots (if appropriate):

[codecov-commenter]

Codecov Report

Merging #383 (b62200c) into master (f51adfc) will not change coverage.
The diff coverage is n/a.

@@            Coverage Diff            @@
##            master      #383   +/-   ##
=========================================
  Coverage   100.00%   100.00%           
=========================================
  Files           80        80           
  Lines         2936      2936           
  Branches       546       546           
=========================================
  Hits          2936      2936           

Impacted Files	Coverage Δ
...ob/trailingTradeIndicator/step/get-trading-view.js	100.00% <ø> (ø)

---

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update aa9e9ff...b62200c. Read the comment docs.

[Rayn0r]

I checked out fix/refactor-tradingview and had the docker images built.
Things look promising after docker-compose ... -up. The Logs show TV data again:

[chrisleekr]

That is good. Try to run a few days to see how it goes.

[Rayn0r]

My results should be taken with a grain of salt, since I'm still running Ubuntu 18.04 and docker version 3.7 is not yet supported (I put 3.3 on the docker.yml )and even npm is warning about:

npm WARN read-shrinkwrap This version of npm is compatible with lockfileVersion@1, but package-lock.json was generated for lockfileVersion@2. I'll try to do my best with it!

But I'll let it run for a few days and see how it performs.
Perhaps @thesam1545 or @atol71 could run a test as well.

[chrisleekr]

@Rayn0r I am running Ubuntu 18.04 as well

$ lsb_release  -a
No LSB modules are available.
Distributor ID:	Ubuntu
Description:	Ubuntu 18.04.5 LTS
Release:	18.04
Codename:	bionic

And I don't have an issue running docker compose 3.7

My docker-compose version is

$ docker-compose -v
docker-compose version 1.26.2, build eefe0d31