Configuration¶

Configure Komandorr to fit your infrastructure and monitoring needs.

Configuration Overview¶

Komandorr can be configured through multiple methods:

Configuration Files¶

JSON-based configuration files for persistent settings.

Environment Variables →

Web Interface¶

Runtime configuration through the dashboard UI.

Services Config →

Environment Variables¶

Docker-friendly environment-based configuration.

Plex Setup →

Configuration Files¶

Main configuration files:

File	Purpose	Location
`config.json`	Global settings	`backend/data/config.json`
`services.json`	Service definitions	`backend/data/services.json`
`komandorr.db`	SQLite database	`backend/data/komandorr.db`

Quick Configuration¶

Minimal Setup¶

{
  "check_interval": 60,
  "admin_password": "your-secure-password"
}

Full Configuration¶

{
  "check_interval": 60,
  "log_level": "INFO",
  "admin_password": "your-secure-password",
  "plex": {
    "url": "http://plex-server:32400",
    "token": "your-plex-token"
  },
  "traffic": {
    "enabled": true,
    "interface": "eth0"
  }
}

Configuration Topics¶

Environment Variables - Docker and system environment configuration
Services - Service monitoring configuration
Plex Integration - Plex Media Server setup
Traffic Agent - Network traffic monitoring configuration

Best Practices¶

Use Environment Variables for sensitive data (tokens, passwords)
Version Control configuration files (excluding secrets)
Document Changes when modifying default settings
Test Configuration in non-production first
Backup Regularly especially before major changes

Security¶

!!! warning "Protect Sensitive Data" - Never commit tokens or passwords to git - Use environment variables for secrets - Restrict file permissions: chmod 600 config.json - Rotate credentials regularly - Use strong passwords