Environment Configuration

This document provides a comprehensive guide to all environment variables that control the Signal trading system's behavior, API integrations, and feature flags. The system uses 67+ environment variables to configure everything from database connections to AI model selection and trading strategy parameters.

For information about Docker deployment and process management, see Docker and Process Management. For details about the build system, see Build System and Dependencies.

Configuration Architecture

The environment configuration system operates through three primary layers: environment variables, Redis-based runtime settings, and feature flag transformations that control both trading logic and user interface behavior.

Configuration Flow

Configuration Categories

The environment variables are organized into 13 distinct categories, each controlling specific aspects of the trading system:

Category	Variables	Purpose
Database Configuration	4 variables	MongoDB and Redis connections
API Keys	11 variables	AI providers and external services
Social Media	5 variables	Mastodon and Telegram integration
Security & Debug	3 variables	JWT, licensing, and debug modes
Trading Configuration	5 variables	Cryptocurrency pair enablement
Webhook Integration	2 variables	External trading system communication
App Features	2 variables	Frontend application control
Prefetch Control	4 variables	Data fetching optimization
Chat Features	9 variables	AI consultation capabilities
Telegram Features	5 variables	Bot notification control
Bootstrap	1 variable	System initialization
Ladder Configuration	4 variables	Trading ladder parameters
Report TTL	3 variables	Cache duration settings

Database and Connection Configuration

The system requires connections to MongoDB for persistent storage and Redis for configuration and caching.

Database Connection Variables

MongoDB Configuration:

• CC_MONGO_CONNECTION_STRING: Full MongoDB connection string including authentication and database name
• Used by SignalDbService and BacktestDbService for trade history and performance analytics

Redis Configuration:

• CC_REDIS_HOST, CC_REDIS_PORT: Redis server connection details
• CC_REDIS_USER, CC_REDIS_PASSWORD: Authentication credentials
• Connected through SettingsConnectionService extending BaseMap with cc-settings namespace

AI Provider Integration

The system supports multiple AI providers for trading decision-making, with configurable API keys for each service.

AI Provider Configuration

Supported AI Providers:

• HuggingFace: Primary provider with openai/gpt-oss-120b and DeepSeek models
• xAI: Grok-3 and Grok-3-mini models
• Ollama: Local inference with gpt-oss:120b and deepseek models
• OpenAI/Claude/Mistral: Commercial API providers
• Perplexity/Cohere/Alibaba: Additional inference options

The InferenceMetaService handles model selection based on isInferenceSelection0 through isInferenceSelection7 feature flags.

Trading System Configuration

Trading behavior is controlled through cryptocurrency pair enablement, webhook integration, and ladder configuration parameters.

Trading Control Variables

Trading Pair Control:

• CC_ENABLE_TRADE: Master switch for all trading functionality
• Individual pair enablement: CC_ENABLE_BTCUSDT, CC_ENABLE_ETHUSDT, etc.
• Used by SignalLogicService.commitBuySignal() to filter allowed trading pairs

Webhook Configuration:

• CC_WEBHOOK_URL: External trading system endpoint for order execution
• CC_WEBHOOK_ENABLE: Boolean flag to activate webhook integration
• Processed by WebhookService for external system communication

Ladder Trading Parameters:

• CC_LADDER_LOWER_STEP, CC_LADDER_UPPER_STEP: Price step calculations
• CC_LADDER_BUY_USDT: Default buy amount in USDT
• CC_LADDER_COMMISSION: Commission rate for P&L calculations

Social Media and Notification Configuration

The system integrates with Telegram for notifications and Mastodon for market sentiment analysis.

Social Media Integration

Telegram Bot Setup:

• CC_TELEGRAM_BOT: Bot username or identifier
• CC_TELEGRAM_TOKEN: API token from BotFather
• CC_TELEGRAM_CHANNEL: Target channel for notifications
• Used by TelegramWebService for publishBuySignal(), publishCloseNotify(), etc.

Mastodon Integration:

• CC_MASTODON_INSTANCE: Mastodon server URL
• CC_MASTODON_ACCESS_TOKEN: Authentication token
• Connected through MastodonService for fetch_mastodon_news() functionality

Telegram Feature Control:

• Five feature flags control specific Telegram functionality
• Managed by FeatureConnectionService with getIsTelegram*Enable() methods
• Integrated with notification filtering in TelegramWebService

Feature Flags and Chat Configuration

The system provides granular control over AI consultation features and data prefetching through environment-controlled feature flags.

Chat Features Configuration

Chat Feature Control:

• Nine feature flags control which data types are available to AI agents
• CC_CHAT_ENABLE_LONG_SIGNALS, CC_CHAT_ENABLE_SHORT_SIGNALS, CC_CHAT_ENABLE_SWING_SIGNALS: Trading signal data access
• CC_CHAT_ENABLE_MASTODON_NEWS, CC_CHAT_ENABLE_TWITTER_NEWS: Social media sentiment analysis
• CC_CHAT_ENABLE_VOLUME_DATA, CC_CHAT_ENABLE_WHALE_DATA: Market microstructure analysis
• CC_CHAT_ENABLE_PRICE_DATA, CC_CHAT_ENABLE_SLOPE_DATA: Technical analysis data

Prefetch Optimization:

• Four prefetch flags control data caching behavior
• CC_ENABLE_TWITTER_PREFETCH, CC_ENABLE_MASTODON_PREFETCH: Social media data caching
• CC_ENABLE_PRICE_FUNCTION_PREFETCH, CC_ENABLE_TREND_FUNCTION_PREFETCH: Market data caching
• Improves agent response times by pre-loading frequently accessed data

Agent Tool Integration:

• Feature flags directly control which tools are available to cryptocurrency consultant agents
• Each agent (BTC, ETH, BNB, XRP, SOL) has access to enabled tools based on these settings
• Tools include fetch_*_term_signals, fetch_*_history, fetch_mastodon/twitter_news, fetch_volume/whale/book_data

Security and Application Configuration

The system includes security controls, debug settings, and application feature toggles for production deployment.

Security and App Control

Variable	Purpose	Integration Point
CC_ENABLE_DEBUG	Debug mode activation	Logging and error reporting
CC_JWT_SECRET	JSON Web Token signing key	Authentication middleware
CC_LICENSE_KEY	System licensing validation	Application startup
CC_BOOTSTRAP_FINISH_ORDERS	Bootstrap completion flag	System initialization
CC_ENABLE_SETUP_APP	Setup interface availability	Frontend application routing
CC_ENABLE_CHAT_APP	Chat interface availability	Agent consultation access

Report TTL Configuration:

• CC_MASTODON_REPORT_TTL: Cache duration for Mastodon reports
• CC_TWITTER_REPORT_TTL: Cache duration for Twitter reports
• CC_TREND_DATA_REPORT_TTL: Cache duration for trend analysis reports

These variables control cache expiration for social media and market data reports, balancing data freshness with API rate limits.

Runtime Configuration Management

Environment variables are transformed into runtime settings through the Redis-based configuration system, enabling dynamic behavior modification without restart.

Configuration Storage Architecture

Configuration Flow:

1. Environment variables initialize Redis settings on startup
2. SettingsConnectionService provides type-safe access to configuration values
3. FeatureConnectionService manages 8 feature flag methods for advanced behavior control
4. Business logic services query configuration for runtime decision-making

Key Service Methods:

• SettingsConnectionService.getValue(): Generic configuration retrieval
• FeatureConnectionService.getIsTelegramBuySignalEnable(): Notification control
• FeatureConnectionService.getIsSignalLogicTakeProfitEnable(): Trading logic control

This architecture enables dynamic configuration changes through the Redis store while maintaining type safety and consistent behavior across all system components.