config.yml file located in the project root. When the file changes on disk, MonoRelay detects the modification via watchfiles and reloads the configuration in place — no restart required. The server, routing rules, provider keys, and all other settings are applied to the next incoming request immediately after reload.
Full config structure
The annotated skeleton below shows every top-level section. Each section is optional; MonoRelay applies sensible defaults for any key you omit.config.yml
Top-level sections
server section parameters
If
access_key is left blank in config.yml, MonoRelay generates a random UUID at startup and logs it. Set an explicit key before exposing the server on a public network.Hot-reload
MonoRelay watchesconfig.yml with watchfiles. When a change is detected the config is reloaded atomically — in-flight requests are not interrupted. Saves performed through the management API use an atomic rename (write to a temp file, then replace) to prevent the watcher from reading a partial file.
Related pages
- Configuring AI providers — add and tune each upstream provider
- Model routing and aliases — control which model goes to which provider
- API key rotation and rate limiting — manage multiple keys per provider