This chapter serves as a supplementary material for the column - building a personal quantitative platform with low thresholds. This article continues to explain how the platform realizes custom early warning, and the platform and the early warning information of flush flush communicate in real-time synchronously.
The following is a practical case to explain how the platform displays the warning information of the flush software in the chart of tradingview, and how the line drawing warning set and drawn by the platform itself is displayed in the flush warning interface (this can be done by phone/SMS notify the user).
1. Tradingview original information storage and loading
In the last issue, I talked about the storage and loading of various information such as tradingview charts (such as historical line drawing analysis, logs, alerts, transaction records, etc.), and the function is implemented in the shared code saveload_backend package. See an open source: GitHub - tradingview/saveload_backend .
The above case is implemented with Django (web service), Postgresql (database). You can change the Postgresql database to your own mongoDB/Mysql database. Django can be replaced with its own Flask (it doesn't matter if it is not, because the storage needs to open another web service and port).
The directory structure is improved as follows:
Add your own application adogviews to the api, peak_finder (find peaks, which are other uses).
Add your own warning alert in V11.