-
Notifications
You must be signed in to change notification settings - Fork 333
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
docs: add document for custom builtin plugin
- Loading branch information
1 parent
fdf3e24
commit 5cf5bb7
Showing
2 changed files
with
90 additions
and
0 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,45 @@ | ||
--- | ||
sidebar_position: 4 | ||
title: Custom Builtin Plugin | ||
--- | ||
|
||
In Tailchat's plugin center, you can see that the system has builtin some plugins for users to install by default, and these plugins cannot be uninstalled. For self-deployed enterprise users, it is particularly important to have all members install the enterprise or other preset plugins by default. | ||
|
||
Next we will learn how to customize the builtin plugin list | ||
|
||
*Because plugins are loaded very early, Tailchat is designed to compile the list of builtin plugins into the source code to ensure that the page loads as quickly as possible. Therefore you need to compile the image manually* | ||
|
||
First you need to clone the source code: | ||
|
||
```bash | ||
git clone https://github.com/msgbyte/tailchat.git | ||
``` | ||
|
||
Modify the builtin plugin list: | ||
|
||
```bash | ||
cd tailchat | ||
vim client/web/src/plugin/builtin.ts | ||
``` | ||
|
||
Add your configuration file (generally found in the `manifest.json` file in the plugin directory) to the exported variable `builtinPlugins` array according to the existing plugin list format. | ||
|
||
:::info | ||
The list of existing plugins can be seen here [Plugin List](/docs/plugin-list/fe) | ||
::: | ||
|
||
When the editing is completed, save it and make sure the current directory is in the root directory of tailchat. At this point you should be able to see the `Dockerfile` file directly in your directory. | ||
|
||
Execute the command to compile your own image | ||
|
||
```bash | ||
docker build . -t tailchat | ||
``` | ||
|
||
Where `.` represents the current directory, `-t tailchat` represents the compiled tag is `tailchat`, which can be read directly by the `docker-compose.yml` file | ||
|
||
After the compilation is completed, just start it according to the normal operation: `docker compose up -d` | ||
|
||
:::info | ||
If you compile the image yourself, it is recommended to configure it above **2C4G** | ||
::: |
45 changes: 45 additions & 0 deletions
45
.../docusaurus-plugin-content-docs/current/advanced-usage/custom-builtin-plugin.md
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,45 @@ | ||
--- | ||
sidebar_position: 4 | ||
title: 自定义内置插件 | ||
--- | ||
|
||
在 Tailchat 的插件中心中可以看到系统已经内置了一部分插件默认给用户安装,且这部分插件是不可被卸载的。而对于自部署的企业用户来说,让所有的成员都默认安装上企业或者预设好的其他插件尤为重要。 | ||
|
||
接下来我们将学习如何自定义内置插件列表 | ||
|
||
*因为插件的加载时机很早,因此在 Tailchat 的设计中会将内置插件列表编译到源码中以确保尽可能快的加载页面。因此你需要手动编译镜像* | ||
|
||
首先需要下载源码: | ||
|
||
```bash | ||
git clone https://github.com/msgbyte/tailchat.git | ||
``` | ||
|
||
修改内置插件列表: | ||
|
||
```bash | ||
cd tailchat | ||
vim client/web/src/plugin/builtin.ts | ||
``` | ||
|
||
将你的配置文件(一般可以在插件目录的`manifest.json`文件中找到)按照已有的插件列表格式添加到导出的变量`builtinPlugins` 数组中。 | ||
|
||
:::info | ||
已有的插件列表可以在这里看到 [插件列表](/docs/plugin-list/fe) | ||
::: | ||
|
||
当编辑完成后保存,确保当前目录在tailchat的根目录。此时你的目录下应该可以直接看到 `Dockerfile` 文件 | ||
|
||
执行命令编译自己的镜像 | ||
|
||
```bash | ||
docker build . -t tailchat | ||
``` | ||
|
||
其中 `.` 表示当前目录,`-t tailchat` 表示编译的标签是 `tailchat`, 这可以直接被 `docker-compose.yml` 文件读取 | ||
|
||
编译完成后按照正常操作启动即可 `docker compose up -d` | ||
|
||
:::info | ||
自己编译镜像建议配置在 **2C4G** 以上 | ||
::: |