TBOT on TradingBoat (Page 3)

Sign in Subscribe

More issues

Deploying TradingBoat Docker on Windows: A Step-by-Step Guide

Background When it comes to Docker on Windows, the most challenging part is installing Docker Desktop on your computer. There are three major steps to follow: 1. Install Windows Subsystem Linux Version 2: WSL2 2. Install Docker Desktop 3. Install TradingBoat Docker The most challenging parts are #1 and #2,

Deploying TradingBoat Docker on a Public Cloud Computer Using AWS EC2

Introduction This article presumes you have already installed the TradingBoat Docker on your local machine, and are familiar with launching TradingBoat Docker and utilizing the dotenv file to manage the TradingBoat application. If not, please refer to the README file . After completing the local setup, you may want to run

Link Interactive Brokers to TradingView via Ngrok

This Docker, TradingBoat is designed to launch the Trading Robot, which converts TradingView Alerts to Interactive Brokers. Once you understand the component applications inside the Docker containers, you can launch them on your own server, if desired instead of using Docker

Converting TradingView PineScript Alerts into Interactive Brokers Orders

TradingView dispatches alert messages using the HTTPS protocol. To receive these alert messages, the trading bot needs an HTTP server. Upon receiving the alert messages, the trading bot decodes them and places orders with Interactive Brokers accordingly.

How to Use a DotEnv File to Control TradingBoat

Introduction In this section, you will learn how to control TradingBoat using environment variables in a DotEnv file. TradingBoat consists of several software components, such as TBOT, Redis, TVWB (Flask), and NGROK. These components can either run as part of the Docker-based TradingBoat or on other cloud computing platforms, such

Decoding TradingView Alerts and Mastering ib_insync: A Comprehensive Guide

Introduction Interactive Brokers does not offer back-testing or forward-testing capabilities. However, with the integration of TradingView's strategy or indicator tools, we can supply these informational components to Interactive Brokers. TradingView has the capacity to send alert messages containing TradingView's trading strategy to a Trading Robot, like

Harnessing the Power of Redis for Efficient Trading Operations: A Detailed Look at Redis Pub/Sub and Stream #2

Introduction This article is a continuation of "Harnessing the Power of Redis for Efficient Trading Operations: A Detailed Look at Redis Pub/Sub and Redis Stream - Part 1". Let's imagine you're running 2-3 strategies or indicators on TradingView, and you want to send

Harnessing the Power of Redis for Efficient Trading Operations: A Detailed Look at Redis Pub/Sub and Stream #1

Introduction While developing a trading robot that processes webhook messages from TradingView and places orders through the Interactive Brokers (IB) Insync API, I opted to use a message broker - Redis Pub/Sub. This decision stems from the convenience it offers in handling asynchronous operations. The two operations, i.e.

A Quick Demo of Trading Robot

In this demonstration, we explore the interaction between Tradingview, the Trading Robot (Tradingboat), and Interactive Brokers. Tradingview generates alert messages, which are sent to TradingBoat. TradingBoat then places orders with Interactive Brokers using the TWS Workstation. The session showcases the flow of message data between the components and the user

Optimizing Execution Time: Improving TradingView to Interactive Brokers Delay with AWS Cloud

When deploying the TBOT application on the AWS Cloud, it receives Webhook messages from TradingView PineScript and places orders using the IB Insync API to Interactive Brokers. However, the overall execution time from TradingView to Interactive Brokers was significantly high.