Configuration is optional, default values will be used if no configuration profile is provided.
Viewing the current configuration¶ From the command line¶Run the program with the config argument:
You can also view just a portion of the config by providing a filter argument.
To view just the file/directory config:
From a running instance¶This will show all the current configuration settings, the most important ones for installation are:
Config dir: Where configuration files are stored
Current profile: (shown in the Profile configuration section)
Config file: The configuration file current being used
Data dir: The data storage directory
From a running instance, you can also view just a portion of the configuration by providing a filter argument:
…will show just the model portion of the configuration
A very handy filter is /config database, which will show just the currently configured database connection string.
The default configuation settings can be seen in config.sample.yaml – the file is well-commented with descriptions of the settings.
DON’T just copy this file as your configuration!
Instead, use it as a reference to tweak the configuration to your liking.
NOTE: Not all settings are available on all backends. See the example config for more information.
Command line arguments overrride custom configuration settings, which override default configuration settings.
Editing the configuration for the current profile¶Start the program: lwe
Open the profile’s configuration file in an editor: /config edit
Edit file to taste and save
Most configuration options will be reloaded dynamically after the configuration file is saved, otherwise a restart of the program is required.
Configuring model properties¶To change the properties of a particular LLM model, use the /model command:
/model model_name gpt-3.5-turbo /model temperature 1.0
The /model command works within the models of the currently loaded provider.
NOTE: The attributes that a particular model accepts are beyond the scope of this document. While some attributes can be displayed via command completion in the shell, you are advised to consult the API documentation for the specific provider for a full list of available attributes and their values.
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4