Configuration Management

Edit and manage bot configuration through the dashboard with hot-reloading, validation, and backup support for all system settings.

Overview

ScreenerBot configuration is managed through data/config.toml and can be edited directly in the dashboard. All changes are validated before saving and can be hot-reloaded without restarting the bot.

Single Source of Truth:

All configuration in one TOML file with embedded defaults

Hot Reload:

Apply changes without restarting the bot (most settings)

Metadata-Driven UI:

Dynamic dashboard editor based on schema metadata

Configuration Sections

Core Settings

Essential system configuration

•Main Wallet: Private key for trading operations
•RPC: Solana RPC endpoints and rate limits
•Webserver: Dashboard port, host, and CORS
•SOL Price: Price refresh interval settings

Trading Configuration

Automated trading settings

•Trader: Max positions, buy amount, mode, delays
•Positions: Exit strategies, ROI targets, stop losses
•Swaps: Router preferences, slippage, priority fees
•DCA: Dollar-cost averaging configuration

Data Services

Token and pool data configuration

•Filtering: Token filter criteria and thresholds
•Tokens: Discovery sources, update priorities
•Pools: DEX pool fetching and calculation
•OHLCV: Timeframes, data sources, cache settings

System Settings

Service and monitoring configuration

•Services: Service-specific startup and priorities
•Monitoring: Logging levels, events, connectivity
•Events: Event retention and cleanup policies
•Summary: Summary report generation settings

Dashboard Editor

Visual Configuration Editor

Edit configuration through a user-friendly interface with type-specific editors and real-time validation.

Editor Features

Section Navigation: Browse by category
Field Editors: Numbers, booleans, text inputs
JSON Editors: Complex objects and arrays
Inline Help: Tooltips and descriptions

Validation & Safety

Real-Time Validation: Before saving
Range Checking: Min/max value enforcement
Format Validation: URLs, keys, addresses
Reset Option: Revert to defaults or last saved

Metadata-Driven: Dashboard UI is automatically generated from configuration schema, providing a dynamic form interface for all settings.

Hot Reload

Configuration Without Restart

Most configuration changes can be applied without restarting the bot using the hot-reload feature.

Reload Process

Save Changes

Update config via dashboard editor

Trigger Reload

Click reload button or call API

Services Update

Config picked up automatically

Verify Changes

Check logs for reload confirmation

Important Notes

Some changes require service restart (noted in UI)
RPC endpoints need full bot restart
Webserver port changes require restart
Trading config hot-reloads instantly
Filter criteria updates immediately

Export & Import

Configuration Backup & Migration

Export and import configuration for backup, migration, or sharing between instances.

Export Configuration

Download current config as TOML file
Includes all sections and settings
Preserves comments and formatting
One-click download from dashboard

Import Configuration

Upload TOML file to replace current config
Full validation before applying
Automatic backup of current config
Preview changes before confirming

Best Practice: Always export and backup your config before making major changes or importing new configuration files.

Configuration File

Configuration File Details

Configuration is stored in data/config.toml. Use this dashboard interface for all configuration changes. Manual file editing is only recommended for advanced users in specific situations.

Note: Config structure may change between updates. Always use the dashboard to ensure your settings stay valid and properly migrated.

→ See Manual Config File Reference

File Location:

data/config.toml

Format:

TOML (Tom's Obvious, Minimal Language)

Comments:

Use # for inline documentation

Editing:

Use dashboard (recommended) or text editor (advanced)

Defaults:

Embedded defaults used if values not specified

Validation:

Auto-checked on load and reload

Security Considerations

Configuration Security

Sensitive Data Protection

Private Keys: Never expose in logs or API responses
File Permissions: Restrict config.toml to owner only
Dashboard Access: Protect with firewall or SSH tunnel
Backup Security: Encrypt exported configs containing private keys

Best Security Practices

Use dedicated wallet for production trading
Keep config files secure and backed up
Regularly rotate API keys and RPC endpoints
Review config permissions after system updates

Best Practices