Configuration Overview
RUSEON Core uses a flexible configuration system that combines a YAML file for initial setup and an internal BadgerDB database for runtime state.
Configuration File
By default, the server looks for config.yaml in the working directory. This file contains core server settings, authentication secrets, event subscriptions, and initial camera and tag definitions.
State Migration
IMPORTANT
When RUSEON Core starts for the very first time, it reads the cameras and global_tags sections from config.yaml and migrates them into the internal BadgerDB database. After migration, these sections are automatically cleared from the YAML file.
Subsequent changes to cameras and tags should be performed via the API or Web UI, as changes to config.yaml for these entities will not take effect once they are in the database. Core server settings, authentication, and event configurations remain in the YAML file and can be updated there.