feat: update config for damocles manager

docs/operation/deploy-a-cs.md

@@ -279,6 +279,10 @@ List all miner ids that have connected to sophon-miner.
 $ ./sophon-miner address list
 ```
 
+### Configure unified entry for chain service
+
+Due to the existence of multiple chain service components, it can be cumbersome for downstream components to connect to multiple chain service components of the same chain service. Additionally, it requires configuring multiple entry points for the chain services. To simplify this process and provide a unified entry point for chain services, you can use sophon-gateway to proxy requests for other chain services. [configure unified entry](https://sophon.venus-fil.io/zh/operation/sophon-gateway.html#%E4%BD%BF%E7%94%A8-gateway-%E4%BB%A3%E7%90%86%E5%AF%B9%E5%85%B6%E4%BB%96%E7%BA%BF%E4%B8%8A%E7%BB%84%E4%BB%B6%E7%9A%84%E8%AF%B7%E6%B1%82)
+
 ## Next steps
 
 Next, please follow this [guide](join-a-cs.md) to connect to the Sophon service you just deployed!

docs/operation/join-a-cs.md

@@ -180,7 +180,7 @@ Pls keep the wallet unlock state. If the state is locked , it will block sealer
 
 :::
 
-## Install Damocles
+## Install damocles
 
 Download source code.
 
@@ -192,6 +192,7 @@ Compile `damocles`.
 
 ```bash
 $ cd damocles
+$ git checkout <LATEST_RELEASE>
 $ make all
 ```
 
@@ -236,21 +237,37 @@ You will see logs similar to the following once successfully created new miner-i
 
 ### damocles-manager configurations
 
-Tailor `~/.damocles-manager/sector-manager.cfg` to your own hardware. Detailed instructions on each configurations could be found [here](/zh/cluster/Venus-Sector-Manager).
+Tailor `~/.damocles-manager/sector-manager.cfg` to your own hardware. Detailed instructions on each configurations could be found [here](/zh/cluster/damocles-manager).
 
 ```toml
 [Common]
   [Common.API]
-    # *mandatory* node address (chain service)
-    Chain = "/ip4/{api_host}/tcp/{api_port}"
-    # *mandatory* messager address (chain service)
-    Messager = "/ip4/{api_host}/tcp/{api_port}"
-    # market node address
-    # Market = "/ip4/{api_host}/tcp/{api_port}"
-    # *mandatory* gateway address (chain service)
-    Gateway = "/ip4/{api_host}/tcp/{api_port}"
-    # *mandatory* authentication token (chain service)
-    Token = "{auth token}"
+  # Gateway service infos, required, string type
+  # Fill in according to the actual situation of the service used
+  # For each one contained, if the item is valid as a token-included-info-string ("{token}:{multiaddr}"), the token included would be used to construct the rpc client instead of the common token.
+  Gateway = ["/ip4/{api_host}/tcp/{api_port}"]
+
+  # common token for services, required, string type
+  # Fill in according to the actual situation of the service used
+  Token = "{some token}"
+
+  # Chain service info, optional, string type
+  # Fill in according to the actual situation of the service used
+  # If the field is valid as a token-included-info-string ("{token}:{multiaddr}"), the token included would be used to construct the rpc client instead of the common token.
+  # If not set, use value of Gateway as default 
+  Chain = "/ip4/{api_host}/tcp/{api_port}"
+
+  # Message service info, optional, string type
+  # Fill in according to the actual situation of the service used
+  # If the field is valid as a token-included-info-string ("{token}:{multiaddr}"), the token included would be used to construct the rpc client instead of the common token.
+  # If not set, use value of Gateway as default 
+  Messager = "/ip4/{api_host}/tcp/{api_port}"
+
+  # Market service info, optional, string type
+  # Fill in according to the actual situation of the service used
+  # If the field is valid as a token-included-info-string ("{token}:{multiaddr}"), the token included would be used to construct the rpc client instead of the common token.
+  # If not set, use value of Gateway as default 
+  Market = "/ip4/{api_host}/tcp/{api_port}"
 
 [[Common.PieceStores]]
   # *mandatory*
@@ -354,11 +371,11 @@ Attach permanent storage and init directories.
 $ ./dist/bin/damocles-worker store file-init -l <dir1>
 ```
 
-Plan CPU cores, numa, etc for eahc sealing tasks and tailor your configuration file to it. The following is an example configuration for `damocles-worker`. More detailed instructions on each configurations could be found [here](/zh/cluster/Venus-Worker-c)
+Plan CPU cores, numa, etc for eahc sealing tasks and tailor your configuration file to it. The following is an example configuration for `damocles-worker`. More detailed instructions on each configurations could be found [here](/zh/cluster/damocles-worker-c)
 
 ```toml
 [worker]
-  # optional, instance name of venus-sector-manager
+  # optional, instance name of damocles-manager
   # name = "bytest"
   # rpc_server.host = "0.0.0.0"
   # rpc_server.port = 17890
@@ -369,7 +386,7 @@ Plan CPU cores, numa, etc for eahc sealing tasks and tailor your configuration f
   # piece_token = "{auth token}"
 
 [sealing]
-  # miner IDs that this venus-worker can serve; Ex: [22908, 11034, 191107]
+  # miner IDs that this damocles-worker can serve; Ex: [22908, 11034, 191107]
   allowed_miners = [33680]
   allowed_sizes = ["32GiB","64GiB"]
   # When set to ture, you will need to configure `piece_token` in `sector_manager`

docs/zh/operation/deploy-a-cs.md

@@ -349,6 +349,11 @@ $ ./sophon-miner address start <MINER_ID>
 $ ./sophon-miner address stop <MINER_ID>
 ```
 
+## 配置链服务统一入口
+
+因为链服务组件比较多, 当下游组件想要链接同一个链服务的多个链服务组件时, 配置会比较繁琐, 并且需要提供多个链服务的入口.
+可以使用 `sophon-gateway` 代理其他链服务的请求, 对外提供一个统一的链服务入口. [部署统一链服务入口](https://sophon.venus-fil.io/zh/operation/sophon-gateway.html#%E4%BD%BF%E7%94%A8-gateway-%E4%BB%A3%E7%90%86%E5%AF%B9%E5%85%B6%E4%BB%96%E7%BA%BF%E4%B8%8A%E7%BB%84%E4%BB%B6%E7%9A%84%E8%AF%B7%E6%B1%82)
+
 ## 启动 droplet（可选）
 
 `droplet` 可以作为链服务组件之一来进行部署，具体部署文档请参考[文档](https://droplet.venus-fil.io/zh/operation/)

docs/zh/operation/join-a-cs.md

@@ -271,16 +271,32 @@ $ ./damocles-manager util miner create
 ```toml
 [Common]
   [Common.API]
-    # 链服务地址，必填项，字符串类型
-    Chain = "/ip4/{api_host}/tcp/{api_port}"
-    # 消息服务地址，必填项，字符串类型
-    Messager = "/ip4/{api_host}/tcp/{api_port}"
-    # 市场服务地址，封装真实数据时为必填项，字符串类型，CC 数据非必填项
-    # Market = "/ip4/{api_host}/tcp/{api_port}"
-    # 网关服务地址，必填项，字符串类型
-    Gateway = "/ip4/{api_host}/tcp/{api_port}"
-    # 服务 token，必填项，字符串类型
-    Token = "{auth token}"
+  # 网关服务地址，必填项，字符串类型
+  # 根据所使用的服务实际情况填写
+  # 对于每一条信息，如果使用了合法的 "{token}:{multiaddr}" 格式，构造客户端时将使用本字段中提取的 token，否则使用通用 sophon-auth 产生的 token
+  Gateway = ["/ip4/{api_host}/tcp/{api_port}"]
+
+  # 链服务信息，可选项，字符串类型
+  # 根据所使用的服务实际情况填写
+  # 如果使用了合法的 "{token}:{multiaddr}" 格式，构造客户端时将使用本字段中提取的 token，否则使用通用 sophon-auth 产生的 token
+  # 如果不填写，会默认使用 Gateway 的地址和 token 作为链服务的入口 
+  Chain = "/ip4/{api_host}/tcp/{api_port}"
+
+  # 消息服务信息，可选项，字符串类型
+  # 根据所使用的服务实际情况填写
+  # 如果使用了合法的 "{token}:{multiaddr}" 格式，构造客户端时将使用本字段中提取的 token，否则使用通用 sophon-auth 产生的 token
+  # 如果不填写，会默认使用 Gateway 的地址和 token 作为消息服务的入口 
+  Messager = "/ip4/{api_host}/tcp/{api_port}"
+
+  # 市场服务信息，可选项，字符串类型
+  # 根据所使用的服务实际情况填写
+  # 如果使用了合法的 "{token}:{multiaddr}" 格式，构造客户端时将使用本字段中提取的 token，否则使用通用 sophon-auth 产生的 token
+  # 如果不填写，会默认使用 Gateway 的地址和 token 作为消息服务的入口 
+  Market = "/ip4/{api_host}/tcp/{api_port}"
+
+  # 服务 sophon-auth 产生的 token，必填项，字符串类型
+  # 根据所使用的服务实际情况填写
+  Token = "{some token}"
 
 [[Common.PieceStores]]
   # 路径，必填项，字符串类型