Connectors

A connector is a small backend that speaks to an upstream feed and answers the chart in the market-data-v1 protocol. The chart ships a provider for each one, so once a connector is running, its instruments show up in search with no extra code.

At a glance

The default base URLs come from dataSourceRegistry in the core. Any of them can be overridden at runtime with marketDataProviderRegistry.setConfig(id, { baseUrl }).

Run them locally

The connectors live in their own repositories, cloned next to the chart repository rather than inside it. You need git, Go 1.21 or later, and uv with Python 3.12; dependencies download on first run.

pnpm setup:backends

pnpm dev -c all               # dev server + gotdx, binance, baostock (mt5 excluded)
pnpm dev -c gotdx baostock    # dev server + the ones you name
pnpm dev -c mt5               # MT5 must be named explicitly

pnpm connector                # gotdx + binance + baostock
pnpm connector baostock       # just one

Logs from every process share one terminal, prefixed [vite], [gotdx], [binance], [baostock] and [mt5]. The dev server proxies /api/public to port 8080 and /api/stock to port 8000.

Each source

GOTDX

gotdx reads Tongdaxin quotes through GoTDX-Connector. Start it with pnpm connector gotdx (it runs go run ./services/tdx-api).

TradingView and BaoStock

Baostock-Tradingview-Connector is one FastAPI service (uv run python ./server.py) behind three source ids: tradingview for global historical bars, baostock for A-share K-lines from BaoStock, and finshare for China futures. Start it with pnpm connector baostock.

Binance depth

The Binance service in GoTDX-Connector proxies Binance's depth stream as server-sent events. It is not a K-line provider and has no source id. The core consumes it through BinanceSSESource and DepthConnector, which feed the order-book heatmap. DEFAULT_BINANCE_SSE_URL points at http://localhost:8081/api/binance/depth-events.

MT5

KCQ-MT5-connector reads from a logged-in MT5 (Exness) terminal, so it only runs on Windows. That is why all leaves it out. Its provider in the core also wires a live-bars stream (BarsLiveSource) against the same base URL. Its instruments trade around the clock and use a UTC session.

Mock

mock needs no backend and is always online. It offers two daily instruments, MOCK-100 and MOCK-10000, and a generated live stream. Use it for rendering tests and demos.

Setup notes for GoTDX-Connector, BaoStock/TradingView and MT5 are kept in their original Chinese: GoTDX-Connector, BaoStock / TradingView, MT5.

How kcq.nebutra.com runs them

The hosted workstation at kcq.nebutra.com/app runs GOTDX, TradingView and Binance depth inside the same Fly Machine as the static site, in Singapore. A small supervisor starts nginx and the three connectors, restarts each one on its own with capped backoff, and prefixes their logs. If nginx itself cannot stay up, the Machine is replaced.

nginx only forwards the protocol endpoints (probe, instrument search, bars, time share, time-share range, trading calendar) and each connector's live-bars stream. Everything else under /market/ is a 404. Requests are rate-limited and connection-capped per client, and Binance depth accepts only btcusdt and ethusdt. GOTDX runs in the Asia/Shanghai time zone so upstream timestamps keep their meaning. Connectors receive no account or trading secrets.

Connector revisions are pinned in apps/kcq/connector-sources.json in the Nebutra-Sailor repository: TsekaLuk/GoTDX-Connector and TsekaLuk/Baostock-Tradingview-Connector, each at a fixed commit. One image is built from those pins, and the deploy is verified with a real search and recent bars, not just process liveness.

Only GOTDX and TradingView appear in the hosted source catalog. BaoStock is withheld until its upstream login succeeds, FinShare while its continuous-contract history is stale, and MT5 because it needs a Windows host.

Next