
* chat item table * perf: chat item save * docs * limit * docs * docs * perf: node card * docs * docs
2.2 KiB
sidebar_position
sidebar_position |
---|
1 |
Quick Introduction
Due to the limitations of environment variables in configuring complex content, the new version of FastGPT uses ConfigMap to mount the configuration file. You can see the default configuration file in client/data/config.json
. You can refer to docker-compose deployment to mount the configuration file.
In the development environment, you need to make a copy of config.json
as config.local.json
for it to take effect.
This configuration file contains customization of the frontend page, system-level parameters, and AI dialogue models, etc.
Note: The configuration instructions below are only a partial introduction. You need to mount the entire config.json file and not just a part of it. You can directly modify the provided config.json file based on the instructions below.
Brief Explanation of Basic Fields
Here are some basic configuration fields.
// This configuration controls some styles of the frontend
"FeConfig": {
"show_emptyChat": true, // Whether to display the introduction page when the conversation page is empty
"show_register": false, // Whether to display the registration button (including forget password, register account, and third-party login)
"show_appStore": false, // Whether to display the app store (currently the permission is not properly set, so it is useless to open it)
"show_userDetail": false, // Whether to display user details (account balance, OpenAI binding)
"show_git": true, // Whether to display Git
"systemTitle": "FastGPT", // The title of the system
"authorText": "Made by FastGPT Team.", // Signature
"gitLoginKey": "" // Git login credentials
}
// This configuration file contains system-level parameters
"SystemParams": {
"gitLoginSecret": "", // Git login credentials
"vectorMaxProcess": 15, // Maximum number of processes for vector generation, set in combination with database performance and key
"qaMaxProcess": 15, // Maximum number of processes for QA generation, set in combination with database performance and key
"pgIvfflatProbe": 20 // pg vector search probe. Can be ignored before setting the index, usually only needed for more than 500,000 groups.
},