🍎 docs: add docs for v0.6.0

docs/docs/application/apps/app_chat.md

@@ -1 +1,15 @@
-# App Chat
+# App Chat
+
+The online Chat interface provides the main conversation capabilities, showing the historical conversation records and the application currently in conversation. As shown in the figure below, clicking any smart application will also jump to this interface.
+
+<p align="center">
+  <img src={'/img/app/app_chat_v0.6.jpg'} width="800px" />
+</p>
+
+In the dialogue interface, a series of operations such as refreshing and pausing the dialogue are supported. The specific operation buttons are in the edit box at the bottom right. At the same time, the dialog box also provides a variety of parameter selections, such as model selection, temperature parameter adjustment, file upload, etc.
+
+<p align="center">
+  <img src={'/img/app/app_chat_op_v0.6.jpg'} width="800" />
+</p>
+
+If you find new problems or have good ideas during use, you can also directly post them on Github [issue](https://github.com/eosphoros-ai/DB-GPT/issues) feedback.

docs/docs/application/apps/app_explore.md

@@ -1 +1,17 @@
-# App Explore
+# App Explore
+
+In the new version of DB-GPT V0.6.0, the application management has been comprehensively upgraded. The search square module is mainly used to discover various interesting, fun and useful data applications.KeywordsIn addition to searching for apps, it also provides popular recommendations, comprehensive apps, my favorites, etc.
+
+After the default installation, the previous six application scenarios are retained.
+
+- [Chat Excel](chat_excel.md)
+- Chat Normal
+- [Chat DB](chat_db.md)
+- [Chat DashBoard](chat_dashboard.md)
+- [Chat Data](chat_data.md)
+- [Chat Knowledge Base](chat_knowledge.md)
+
+
+<p align="center">
+  <img src={'/img/app/app_explore_v0.6.jpg'} width="800px" />
+</p>

docs/docs/application/apps/app_manage.md

@@ -1 +1,55 @@
-# App Manage
+# App Manage
+
+The application management panel provides many capabilities. Here we mainly introduce the management of the data intelligence application life cycle, including application creation, editing, deletion, and use.
+
+<p align="center">
+  <img src={'/img/app/app_manage_v0.6.jpg'} width="800px" />
+</p>
+
+As shown in the figure, the application management interface. First, let's take a look at the creation of an application. In DB-GPT, four application creation modes are provided. 
+
+- Multi-agent automatic planning mode
+- Task flow orchestration mode 
+- Single Agent Mode 
+- Native application mode
+
+<p align="center">
+  <img src={'/img/app/app_manage_mode_v0.6.jpg'} width="800px" />
+</p>
+
+Next, we will explain the creation of applications in each mode respectively. Native application mode In the early versions of DB-GPT, six types of native application scenarios were provided, such as `Chat DB`, `Chat Data`, `Chat Dashboard`, `Chat Knowledge Base`, `Chat Normal`, `Chat Excel`, etc. 
+
+By creating a data intelligence application in the native application mode, you can quickly build a similar application based on your own database, knowledge base and other parameters. Click the upper right cornerCreate an applicationbutton, select **Native application mode**, enter the application name and description, click **Sure**
+
+<p align="center">
+  <img src={'/img/app/app_manage_chat_data_v0.6.jpg'} width="800px" />
+</p>
+
+After confirmation, enter the parameter selection panel. As shown in the figure below, we can see selection boxes such as application type, model, temperature, and recommended questions.
+
+<p align="center">
+  <img src={'/img/app/app_manage_chat_data_editor_v0.6.jpg'} width="800px" />
+</p>
+
+Here, we select **Chat Data**  Application, fill in the parameters in order according to the requirements. Note that in the data dialogue application, the parameter column needs to fill in the data source. If you do not have a data source, you need to follow [Data Source Tutorial](../datasources.md) to add it.
+
+
+After completing the parameters, click **Save** to view related applications in the application panel.
+
+<p align="center">
+  <img src={'/img/app/app_manage_app_v0.6.jpg'} width="800px" />
+</p>
+
+Please note that after creating an application, there is a **Publish Application** button. Only after the application is published can it be discovered and used by other users.
+
+<p align="center">
+  <img src={'/img/app/app_manage_app_publish_v0.6.jpg'} width="800px" />
+</p>
+
+Finally, click the **Start a conversation** button to start a conversation with the application you just created.
+
+<p align="center">
+  <img src={'/img/app/app_manage_chat_v0.6.jpg'} width="800px" />
+</p>
+
+In addition, you can also edit and delete applications. Just operate on the corresponding interface.

docs/docs/application/apps/app_usage.md

@@ -1,59 +0,0 @@
-# Data App Usage
-
-Starting with version 0.5.0, the DB-GPT project has natively integrated the management and distribution of data-centric applications. The application management repository is also part of the open-source [dbgpts](https://github.com/eosphoros-ai/dbgpts) project. The [dbgpts](https://github.com/eosphoros-ai/dbgpts) project manages and shares resources categorized into the following:
-
-- [apps](https://github.com/eosphoros-ai/dbgpts/tree/main/apps): These are native intelligent data applications developed using the DB-GPT framework.
-- [workflow](https://github.com/eosphoros-ai/dbgpts/tree/main/workflow): Workflows constructed using the AWEL (Agentic Workflow Expression Language).
-- [agents](https://github.com/eosphoros-ai/dbgpts/tree/main/agents): Intelligent agents that can perform various tasks.
-- [operators](https://github.com/eosphoros-ai/dbgpts/tree/main/operators): Basic operational operators (or symbols) that can be used within workflows.
-
-:::info NOTE
-
-Please note that this tutorial primarily focuses on the installation and use of intelligent agent workflows. For the development of applications, you should refer to the `Development Guide`.
-
-Support for these capabilities is provided from version V0.5.0 onwards. For developers and teams looking to build and distribute their applications through DB-GPT, this structured approach provides both a framework and ecosystem for creating, sharing, and managing data applications effectively.
-:::
-
-Here we introduce the creation of a data intelligence analysis assistant application. This tutorial utilizes the auto-planning capability of Multi-Agents.
-
-The effect is as follows:
-
-<p align="left">
-  <img src={'/img/app/app_analysis.png'} width="720px" />
-</p>
-
-In the application panel, click on `Create Application` and fill in the parameters as shown in the image. It is important to note that the work mode selected here is `auto_plan`. This involves the collaboration of two dependent Agents: 1. DataScientist and 2. Reporter. Both of these agents depend on the resource `database`, and for testing, you can use the default database and data provided in the official tutorial.
-
-Special Note: Currently, in auto-plan mode, the building of applications is conducted through multiple Agents. This project has a number of built-in Agents, which currently include:
-- [CodeEngineer](https://github.com/eosphoros-ai/DB-GPT/blob/main/dbgpt/agent/agents/expand/code_assistant_agent.py)
-- [Reporter](https://github.com/eosphoros-ai/DB-GPT/blob/main/dbgpt/agent/agents/expand/dashboard_assistant_agent.py)
-- [DataScientist](https://github.com/eosphoros-ai/DB-GPT/blob/main/dbgpt/agent/agents/expand/data_scientist_agent.py)
-- [ToolExpert](https://github.com/eosphoros-ai/DB-GPT/blob/main/dbgpt/agent/agents/expand/plugin_assistant_agent.py)
-- [RetrieveSummarizer](https://github.com/eosphoros-ai/DB-GPT/blob/main/dbgpt/agent/agents/expand/retrieve_summary_assistant_agent.py)
-- [Summarizer](https://github.com/eosphoros-ai/DB-GPT/blob/main/dbgpt/agent/agents/expand/summary_assistant_agent.py)
-
-If you wish to expand and implement customized Agents, you can refer to the `Agents Development Guide`.
-
-<p align="left">
-  <img src={'/img/app/app_agents.png'} width="720px" />
-</p>
-
-<p align="left">
-  <img src={'/img/app/app_agent_reporter.jpg'} width="720px" />
-</p>
-
-After adding the necessary information, choose to submit to complete the creation of the application. In the application panel, click the dialogue button to enter the dialogue interface.
-
-<p align="left">
-  <img src={'/img/app/app_list.png'} width="720px" />
-</p>
-
-<p align="left">
-  <img src={'/img/app/app_analysis_black.png'} width="720px" />
-</p>
-
-
-# Summary
-This tutorial is just a simple introduction to application construction. If you are interested in more complex applications, you can achieve more intricate scenarios by orchestrating AWEL workflows and customizing the expansion of Agents.
-
-

docs/docs/application/awel.md

@@ -1 +1,7 @@
-# Use Data App With AWEL
+# Use Data App With AWEL
+
+
+## Reference
+- [AWEL](../awel/awel.md)
+- [AWEL CookBook](../awel/cookbook/)
+- [AWEL Tutorial](../awel/awel_tutorial/)

docs/docs/application/datasources.md

@@ -0,0 +1,14 @@
+# Datasources
+
+The DB-GPT data source module is designed to manage the structured and semi-structured data assets of an enterprise, connect databases, data warehouses, data lakes, etc. to the DB-GPT framework, and quickly build data-based intelligent applications and large models. Currently, DB-GPT supports some common data sources and also supports custom extensions.
+
+<p align="center">
+  <img src={'/img/app/datasource.jpg'} width="800px" />
+</p>
+
+
+You can add data sources through the upper right corner **Add a data source** button to add. In the pop-up dialog box, select the corresponding database type and fill in the required parameters to complete the addition.
+
+<p align="center">
+  <img src={'/img/app/datasource_add.jpg'} width="800px" />
+</p>

docs/docs/application/llms.md

@@ -0,0 +1,15 @@
+# LLMs
+
+In the new version, the location of model management has moved to **Application Management** Under the panel, other functional modules remain unchanged
+
+
+<p align="center">
+  <img src={'/img/app/llms_v0.6.jpg'} width="800px" />
+</p>
+
+
+For the use of multi-model management, please refer to the following documents.
+
+- [Multi-Model Management](../application/advanced_tutorial/smmf.md)
+- [Model Service deployment](../installation/model_service/)
+- [Introduction to the principles of multi-model management](../modules/smmf.md)

docs/docs/application/prompts.md

@@ -0,0 +1,61 @@
+# Prompts
+
+In the actual application development process, Prompt needs to be customized in different scenarios, Agent, RAG and other modules. In order to make the editing and adjustment of Prompt more flexible, an independent Prompt module is created.
+
+## Browse
+
+As shown in the figure below, click **Application Management** ->**Prompt** You can enter the corresponding management interface. The interface displays a custom prompt list by default, and you can manage all prompts.
+
+<p align="center">
+  <img src={'/img/app/prompt_v0.6.jpg'} width="800px" />
+</p>
+
+## Added
+Next, let's see how to create a new prompt. Click the **Add Prompt**  button and the prompt edit box will pop up.
+
+<p align="center">
+  <img src={'/img/app/prompt_add_v0.6.jpg'} width="800px" />
+</p>
+
+We define four types of prompts: 
+- AGENT: Agent Prompt 
+- SCENE: Scene Prompt 
+- NORMAL: Normal prompt word 
+- EVALUATE: Evaluation Mode Prompt
+
+When the AGENT type is selected, all registered agents can be seen in the drop-down list menu, and you can select an agent to set the prompt.
+
+<p align="center">
+  <img src={'/img/app/agent_prompt_v0.6.jpg'} width="400px" />
+</p>
+
+After setting the prompt, a unique UID will be generated. You can bind the corresponding prompt according to the ID when using it.
+
+<p align="center">
+  <img src={'/img/app/agent_prompt_code_v0.6.jpg'} width="800px" />
+</p>
+
+
+## Usage
+
+Enter the AWEL editing interface, as shown below, click **Application Management** -> **Create Workflow**
+
+
+<p align="center">
+  <img src={'/img/app/awel_create.6.jpg'} width="800px" />
+</p>
+
+Find the Agent resource and select the AWEL Layout Agent operator. We can see that each Agent contains the following information: 
+
+- Profile
+- Role
+- Goal
+- Resource (AWELResource): The resource that Agent depends on 
+- AgentConfig(AWELAgentConfig) Agent Config
+- AgentPrompt: Prompt
+
+<p align="center">
+  <img src={'/img/app/agent_prompt_awel_v0.6.jpg'} width="800px" />
+</p>
+
+Click the [+] next to **AgentPrompt**, select the Prompt operator that pops up, and select the corresponding Prompt name or UID in the parameter panel to bind our newly created Prompt to the Agent, and debug the Agent's behavior in turn.

docs/docs/upgrade/v0.6.0.md

@@ -1 +1,184 @@
 # Upgrade To v0.6.0
+
+## Overview
+
+This guide is for upgrading from v0.5.10 to v0.6.0. If you use SQLite, you not need to upgrade the database. If you use MySQL, you need to upgrade the database.
+
+
+## Prepare
+
+### Backup Your Database
+
+To prevent data loss, it is recommended to back up your database before upgrading. The backup way according to your database type.
+
+## Upgrade
+
+### Stop DB-GPT Service
+
+Stop the DB-GPT service according to your start way.
+
+### Upgrade database
+Execute the following SQL to upgrade the database.
+
+:::tip
+The asset files required for the version upgrade are placed [here](https://github.com/eosphoros-ai/DB-GPT/tree/main/assets/schema/upgrade).
+:::
+
+```sql
+USE dbgpt;
+-- chat_history
+ALTER TABLE  chat_history ADD COLUMN `app_code` varchar(255) DEFAULT NULL COMMENT 'App unique code' after `message_ids`;
+
+-- gpts_app
+ALTER TABLE  gpts_app ADD COLUMN `published` varchar(64) DEFAULT 'false' COMMENT 'Has it been published?';
+ALTER TABLE  gpts_app ADD COLUMN `param_need` text DEFAULT NULL COMMENT 'Parameter information supported by the application';
+ALTER TABLE  gpts_app ADD COLUMN `admins` text DEFAULT NULL COMMENT 'administrator';
+
+
+-- connect_config
+ALTER TABLE  connect_config ADD COLUMN `user_name` varchar(255) DEFAULT NULL COMMENT 'user name';
+ALTER TABLE  connect_config ADD COLUMN `user_id` varchar(255) DEFAULT NULL COMMENT 'user id';
+
+-- document_chunk
+ALTER TABLE  document_chunk ADD COLUMN `questions` text DEFAULT NULL COMMENT 'chunk related questions';
+
+-- knowledge_document
+ALTER TABLE  knowledge_document ADD COLUMN `doc_token` varchar(100) DEFAULT NULL COMMENT 'doc token';
+ALTER TABLE  knowledge_document ADD COLUMN `questions` text DEFAULT NULL COMMENT 'document related questions';
+
+-- gpts_messages
+ALTER TABLE  gpts_messages ADD COLUMN `is_success` int(4)  NULL DEFAULT 0 COMMENT 'agent message is success';
+ALTER TABLE  gpts_messages ADD COLUMN `app_code` varchar(255) NOT NULL COMMENT 'Current AI assistant code';
+ALTER TABLE  gpts_messages ADD COLUMN `app_name` varchar(255) NOT NULL COMMENT 'Current AI assistant name';
+ALTER TABLE  gpts_messages ADD COLUMN `resource_info` text DEFAULT NULL  COMMENT 'Current conversation resource info';
+
+-- prompt_manage
+ALTER TABLE  prompt_manage ADD COLUMN `prompt_code` varchar(255) NULL COMMENT 'Prompt code';
+ALTER TABLE  prompt_manage ADD COLUMN `response_schema` text  NULL COMMENT 'Prompt response schema';
+ALTER TABLE  prompt_manage ADD COLUMN `user_code` varchar(128)  NULL COMMENT 'User code';
+
+-- chat_feed_back
+ALTER TABLE  chat_feed_back ADD COLUMN `message_id` varchar(255)  NULL COMMENT 'Message id';
+ALTER TABLE  chat_feed_back ADD COLUMN `feedback_type` varchar(50)  NULL COMMENT 'Feedback type like or unlike';
+ALTER TABLE  chat_feed_back ADD COLUMN `reason_types` varchar(255)  NULL COMMENT 'Feedback reason categories';
+ALTER TABLE  chat_feed_back ADD COLUMN `user_code` varchar(128)  NULL COMMENT 'User code';
+ALTER TABLE  chat_feed_back ADD COLUMN `remark` text NULL COMMENT 'Feedback remark';
+
+-- dbgpt_serve_flow
+ALTER TABLE dbgpt_serve_flow ADD COLUMN `variables` text DEFAULT NULL COMMENT 'Flow variables, JSON format';
+
+-- dbgpt.recommend_question definition
+CREATE TABLE `recommend_question` (
+  `id` bigint(20) unsigned NOT NULL AUTO_INCREMENT COMMENT 'autoincrement id',
+  `gmt_create` timestamp NOT NULL DEFAULT CURRENT_TIMESTAMP COMMENT 'create time',
+  `gmt_modified` timestamp NOT NULL DEFAULT CURRENT_TIMESTAMP ON UPDATE CURRENT_TIMESTAMP COMMENT 'last update time',
+  `app_code` varchar(255) DEFAULT NULL COMMENT 'Current AI assistant code',
+  `question` text DEFAULT NULL COMMENT 'question',
+  `user_code` int(11) DEFAULT NULL COMMENT 'user code',
+  `sys_code` varchar(255) DEFAULT NULL COMMENT 'system app code',
+  `valid` varchar(10) DEFAULT 'true' COMMENT 'is it effective，true/false',
+  `chat_mode` varchar(255) DEFAULT NULL COMMENT 'Conversation scene mode，chat_knowledge...',
+  `params` text DEFAULT NULL COMMENT 'question param',
+  `is_hot_question` varchar(10) DEFAULT 'false' COMMENT 'Is it a popular recommendation question?',
+  PRIMARY KEY (`id`),
+  KEY `idx_rec_q_app_code` (`app_code`)
+) ENGINE=InnoDB AUTO_INCREMENT=1 DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_unicode_ci COMMENT="AI application related recommendation issues";
+
+-- dbgpt.user_recent_apps definition
+CREATE TABLE `user_recent_apps` (
+  `id` bigint(20) unsigned NOT NULL AUTO_INCREMENT COMMENT 'autoincrement id',
+  `gmt_create` timestamp NOT NULL DEFAULT CURRENT_TIMESTAMP COMMENT 'create time',
+  `gmt_modified` timestamp NOT NULL DEFAULT CURRENT_TIMESTAMP ON UPDATE CURRENT_TIMESTAMP COMMENT 'last update time',
+  `app_code` varchar(255) DEFAULT NULL COMMENT 'AI assistant code',
+  `last_accessed` timestamp NULL DEFAULT NULL COMMENT 'User recent usage time',
+  `user_code` varchar(255) DEFAULT NULL COMMENT 'user code',
+  `sys_code` varchar(255) DEFAULT NULL COMMENT 'system app code',
+  PRIMARY KEY (`id`),
+  KEY `idx_user_r_app_code` (`app_code`),
+  KEY `idx_last_accessed` (`last_accessed`),
+  KEY `idx_user_code` (`user_code`)
+) ENGINE=InnoDB AUTO_INCREMENT=1 DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_unicode_ci COMMENT='User recently used apps';
+
+-- dbgpt.dbgpt_serve_file definition
+CREATE TABLE `dbgpt_serve_file` (
+  `id` int NOT NULL AUTO_INCREMENT COMMENT 'Auto increment id',
+  `bucket` varchar(255) NOT NULL COMMENT 'Bucket name',
+  `file_id` varchar(255) NOT NULL COMMENT 'File id',
+  `file_name` varchar(256) NOT NULL COMMENT 'File name',
+  `file_size` int DEFAULT NULL COMMENT 'File size',
+  `storage_type` varchar(32) NOT NULL COMMENT 'Storage type',
+  `storage_path` varchar(512) NOT NULL COMMENT 'Storage path',
+  `uri` varchar(512) NOT NULL COMMENT 'File URI',
+  `custom_metadata` text DEFAULT NULL COMMENT 'Custom metadata, JSON format',
+  `file_hash` varchar(128) DEFAULT NULL COMMENT 'File hash',
+  `user_name` varchar(128) DEFAULT NULL COMMENT 'User name',
+  `sys_code` varchar(128) DEFAULT NULL COMMENT 'System code',
+  `gmt_created` datetime DEFAULT CURRENT_TIMESTAMP COMMENT 'Record creation time',
+  `gmt_modified` datetime DEFAULT CURRENT_TIMESTAMP ON UPDATE CURRENT_TIMESTAMP COMMENT 'Record update time',
+  PRIMARY KEY (`id`),
+  UNIQUE KEY `uk_bucket_file_id` (`bucket`, `file_id`)
+) ENGINE=InnoDB AUTO_INCREMENT=1 DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_unicode_ci;
+
+-- dbgpt.dbgpt_serve_variables definition
+CREATE TABLE `dbgpt_serve_variables` (
+  `id` int NOT NULL AUTO_INCREMENT COMMENT 'Auto increment id',
+  `key` varchar(128) NOT NULL COMMENT 'Variable key',
+  `name` varchar(128) DEFAULT NULL COMMENT 'Variable name',
+  `label` varchar(128) DEFAULT NULL COMMENT 'Variable label',
+  `value` text DEFAULT NULL COMMENT 'Variable value, JSON format',
+  `value_type` varchar(32) DEFAULT NULL COMMENT 'Variable value type(string, int, float, bool)',
+  `category` varchar(32) DEFAULT 'common' COMMENT 'Variable category(common or secret)',
+  `encryption_method` varchar(32) DEFAULT NULL COMMENT 'Variable encryption method(fernet, simple, rsa, aes)',
+  `salt` varchar(128) DEFAULT NULL COMMENT 'Variable salt',
+  `scope` varchar(32) DEFAULT 'global' COMMENT 'Variable scope(global,flow,app,agent,datasource,flow_priv,agent_priv, ""etc)',
+  `scope_key` varchar(256) DEFAULT NULL COMMENT 'Variable scope key, default is empty, for scope is "flow_priv", the scope_key is dag id of flow',
+  `enabled` int DEFAULT 1 COMMENT 'Variable enabled, 0: disabled, 1: enabled',
+  `description` text DEFAULT NULL COMMENT 'Variable description',
+  `user_name` varchar(128) DEFAULT NULL COMMENT 'User name',
+  `sys_code` varchar(128) DEFAULT NULL COMMENT 'System code',
+  `gmt_created` datetime DEFAULT CURRENT_TIMESTAMP COMMENT 'Record creation time',
+  `gmt_modified` datetime DEFAULT CURRENT_TIMESTAMP ON UPDATE CURRENT_TIMESTAMP COMMENT 'Record update time',
+  PRIMARY KEY (`id`),
+  KEY `ix_your_table_name_key` (`key`),
+  KEY `ix_your_table_name_name` (`name`)
+) ENGINE=InnoDB AUTO_INCREMENT=1 DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_unicode_ci;
+
+-- dbgpt.dbgpt_serve_dbgpts_my definition
+CREATE TABLE `dbgpt_serve_dbgpts_my` (
+  `id` int NOT NULL AUTO_INCREMENT COMMENT 'autoincrement id',
+  `name` varchar(255)  NOT NULL COMMENT 'plugin name',
+  `user_name` varchar(255)  DEFAULT NULL COMMENT 'user name',
+  `file_name` varchar(255)  NOT NULL COMMENT 'plugin package file name',
+  `type` varchar(255)  DEFAULT NULL COMMENT 'plugin type',
+  `version` varchar(255)  DEFAULT NULL COMMENT 'plugin version',
+  `use_count` int DEFAULT NULL COMMENT 'plugin total use count',
+  `succ_count` int DEFAULT NULL COMMENT 'plugin total success count',
+  `sys_code` varchar(128) DEFAULT NULL COMMENT 'System code',
+  `gmt_created` TIMESTAMP DEFAULT CURRENT_TIMESTAMP COMMENT 'plugin install time',
+  `gmt_modified` TIMESTAMP DEFAULT CURRENT_TIMESTAMP ON UPDATE CURRENT_TIMESTAMP COMMENT 'update time',
+  PRIMARY KEY (`id`),
+  UNIQUE KEY `name` (`name`, `user_name`),
+  KEY `ix_my_plugin_sys_code` (`sys_code`)
+) ENGINE=InnoDB AUTO_INCREMENT=1 DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_unicode_ci;
+
+-- dbgpt.dbgpt_serve_dbgpts_hub definition
+CREATE TABLE `dbgpt_serve_dbgpts_hub` (
+  `id` int NOT NULL AUTO_INCREMENT COMMENT 'autoincrement id',
+  `name` varchar(255) NOT NULL COMMENT 'plugin name',
+  `description` varchar(255)  NULL COMMENT 'plugin description',
+  `author` varchar(255) DEFAULT NULL COMMENT 'plugin author',
+  `email` varchar(255) DEFAULT NULL COMMENT 'plugin author email',
+  `type` varchar(255) DEFAULT NULL COMMENT 'plugin type',
+  `version` varchar(255) DEFAULT NULL COMMENT 'plugin version',
+  `storage_channel` varchar(255) DEFAULT NULL COMMENT 'plugin storage channel',
+  `storage_url` varchar(255) DEFAULT NULL COMMENT 'plugin download url',
+  `download_param` varchar(255) DEFAULT NULL COMMENT 'plugin download param',
+  `gmt_created` TIMESTAMP DEFAULT CURRENT_TIMESTAMP COMMENT 'plugin upload time',
+  `gmt_modified` TIMESTAMP    DEFAULT CURRENT_TIMESTAMP ON UPDATE CURRENT_TIMESTAMP COMMENT 'update time',
+  `installed` int DEFAULT NULL COMMENT 'plugin already installed count',
+  PRIMARY KEY (`id`),
+  UNIQUE KEY `name` (`name`)
+) ENGINE=InnoDB AUTO_INCREMENT=1 DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_unicode_ci;
+
+```
+

docs/sidebars.js

@@ -288,11 +288,6 @@ const sidebars = {
               id: 'application/apps/app_manage',
               label: "App Manage"
             }, 
-            {
-              type: 'doc',
-              id: 'application/apps/chat_knowledge',
-              label: "Chat Knowledge Base"
-            },
             {
               type: 'doc',
               id: 'application/apps/chat_data',
@@ -308,6 +303,11 @@ const sidebars = {
               id: 'application/apps/chat_db',
               label: "chat DB"
             },
+            {
+              type: 'doc',
+              id: 'application/apps/chat_knowledge',
+              label: "Chat Knowledge Base"
+            },
             {
               type: 'doc',
               id: 'application/apps/chat_dashboard',