Domain Deployment Configuration
This guide documents the domain deployment configuration system for the Zudoku framework, which enables flexible configuration of domain-specific settings and product enablement across different trading platforms.
Configuration Schema Overview
The deployment configuration is managed through a JSON schema (version 1.0) that supports hierarchical settings with global defaults and domain-specific overrides.
Top-Level Structure
Code
Global Settings
The global section defines base configuration values that apply to all domains unless explicitly overridden.
Default Values
Global default values control platform-wide limits and behaviors:
Code
Responsive Flags
Responsive flags control feature availability across different platforms:
Code
Super Settings
The super section contains detailed platform configuration flags, including feature toggles, branding options, and integration settings.
Domain Structure
Each domain configuration follows this structure:
Code
Domain-Specific Settings
Domains can override global default values and responsive flags:
Code
Product Enablement
Each domain specifies which products are enabled:
Code
Common Platform Features
Trading Features
platform.trading: Enables trading capabilitiesplatform.orders: Order managementplatform.positions: Position trackingplatform.tradePanel: Trading panel UIplatform.paperTrading: Paper trading mode
Alert System
platform.alerts: Basic alertsplatform.priceAlert: Price alertsplatform.volumeAlert: Volume alertsplatform.internalAlerts: Internal alert system
Data Features
platform.marketData: Market data accessplatform.economicCalendar: Economic eventsplatform.screener: Stock screenerplatform.crypto: Cryptocurrency data
Community Features
platform.ideas: Trading ideasplatform.socialLogin: Social authenticationplatform.news: News feedplatform.pulse: Pulse feature
UI Components
platform.headerWidget: Header componentsplatform.footerWidget: Footer componentsplatform.logo: Logo displayplatform.themeSwitcher: Theme switching
Export Features
platform.exportData: Data exportplatform.exportImage: Image exportplatform.screenshot: Screenshot functionality
Configuration Examples
Basic Domain Configuration
Code
Trading-Enabled Domain
Code
Operational Procedures
Adding a New Domain
- Prepare Domain Settings: Create the domain configuration object
- Define Product Enablement: Specify which products are enabled for the domain
- Configure Global Overrides: Set any domain-specific default value overrides
- Set Platform Features: Configure super settings for platform behavior
- Validate Configuration: Run configuration validation checks
- Deploy Configuration: Update the deployment-config.json file
- Test Deployment: Verify the domain loads with correct settings
Modifying Domain Settings
- Locate Domain: Find the domain object in the domains array
- Update Settings: Modify the settings object as needed
- Validate Changes: Check that enabled products match available settings
- Test Changes: Deploy and verify functionality
Removing a Domain
- Backup Configuration: Save current state for rollback
- Remove Domain Object: Delete the domain entry from domains array
- Validate Removal: Ensure no orphaned references
- Deploy Changes: Update configuration and verify removal
Configuration Validation
The configuration system supports validation through:
- Schema version checking
- Required field presence
- Product enablement consistency
- Platform setting conflicts
Best Practices
- Inheritance Utilization: Use global defaults to avoid repetition
- Minimal Overrides: Only override what needs to be different per domain
- Product Consistency: Ensure enabled products match the platform's capabilities
- Version Tracking: Maintain schema version compatibility
- Documentation: Keep configuration changes documented with rationale
Troubleshooting
Common Issues:
- Product enabled but corresponding platform features disabled
- Missing required settings for enabled products
- Conflicting global vs domain settings
- Invalid schema structure
Debug Steps:
- Validate JSON syntax
- Check schema version compatibility
- Verify product enablement matches platform features
- Test with minimal domain configuration
- Check browser console for configuration loading errors
Version History
- v1.0: Initial schema with global defaults, domain overrides, and product enablement
- Supports hierarchical configuration inheritance
- Platform feature toggles via super settings
- Responsive flags for mobile/web differentiation
- Product-based enablement system