Configuration

Gordon v7 configuration spans service environment, database setup, port bindings, strategy tuning, and cost modeling.

Sections

• Environment — per-service environment variables, .env file conventions, secrets management, NATS URL, database DSNs, operator tokens, and Binance key rules.
• Database — PostgreSQL schemas (market_data, trading), roles, named reader views, table inventory, and conventions. Source of truth: gordon-migrate/migrations/.
• Ports — service port registry, bind-address env vars, and network exposure model.
• Strategy Parameters — per-strategy parameter reference for the three validated strategies (Supertrend, EWMAC, PSAR) and inventory of the 11 active engines added in gordon-strategy 4.6.x.
• Fees & Costs — Binance Futures VIP 0 fee table, slippage estimates per asset, funding rate model, and the two-model design (FeeModel vs CostModel).
• Assets — supported trading pairs, Binance-native symbol convention, timeframe strings, and data provisioning commands.

Key principles

• Single PostgreSQL instance shared by all services. No SQLite, no dual-backend configurations.
• All secrets and connection strings via environment variables. Never committed to git.
• Net-of-fees always — no backtest result is valid without transaction costs applied.
• 1m candles are the canonical source of truth. Higher timeframes are precomputed by gordon-data.