Overview
Configure your R2R deployment
R2R offers a flexible configuration system that allows you to customize your Retrieval-Augmented Generation (RAG) system. This guide introduces the key concepts and methods for configuring R2R.
Configuration Levels
R2R supports two main levels of configuration:
- Server-side Configuration: Define default configuration for your R2R deployment.
- Runtime Settings: Dynamically override configuration settings when making API calls.
Server-side Configuration
The default settings for the R2R light
installation are specified in the r2r.toml
file.
To create your own custom configuration:
- Create a new file named
my_r2r.toml
in your project directory. - Add only the settings you wish to customize. For example:
- Launch R2R with the CLI using your custom configuration:
R2R will use your specified settings, falling back to the defaults defined in the r2r.toml
for any unspecified options. When doing the R2R full
installation the R2R CLI uses the full.toml
to configure the relevant provider settings.
Runtime Settings
When calling endpoints, like retrieval/search
or retrieval/rag
, you can override server-side configurations on-the-fly. This allows for dynamic control over search settings, model selection, prompt customization, and more.
For example, using the Python SDK:
Refer here to learn more about configuring and dynamically setting your retrieval system.