add volcengine tos storage to support #20

Closed
opened 2026-02-16 11:19:31 -05:00 by yindo · 1 comment
Owner

Originally created by @yaoice on GitHub (Sep 9, 2024).

Originally created by @yaoice on GitHub (Sep 9, 2024).
yindo added the enhancement label 2026-02-16 11:19:31 -05:00
yindo closed this issue 2026-02-16 11:19:31 -05:00
Author
Owner

@dosubot[bot] commented on GitHub (Sep 9, 2024):

To add Volcengine TOS storage support, you can follow the existing pattern for integrating new storage services. Here are the steps:

  1. Define Environment Variables:

    • Add new environment variables for Volcengine TOS similar to the existing ones for S3, Azure Blob, and Aliyun OSS.
  2. Update Configuration:

    • Modify the configuration section to include Volcengine TOS as a storage type.
  3. Implement Storage Integration:

    • Implement the necessary code to handle file operations (upload, download, delete) using Volcengine TOS SDK.

Example Configuration

Add the following environment variables for Volcengine TOS:

- TOS_ENDPOINT: TOS endpoint address
- TOS_BUCKET_NAME: TOS bucket name
- TOS_ACCESS_KEY: TOS Access Key
- TOS_SECRET_KEY: TOS Secret Key
- TOS_REGION: TOS region information

Update Configuration Section

Modify the configuration section to include Volcengine TOS:

- STORAGE_TYPE

  Type of storage facility

  - local (default)
  - s3
  - azure-blob
  - aliyun-oss
  - tos  # Add this line for Volcengine TOS

- TOS_ENDPOINT: TOS endpoint address
- TOS_BUCKET_NAME: TOS bucket name
- TOS_ACCESS_KEY: TOS Access Key
- TOS_SECRET_KEY: TOS Secret Key
- TOS_REGION: TOS region information

Implement Storage Integration

Implement the necessary code to handle file operations using the Volcengine TOS SDK. Ensure you follow the same structure as the existing storage integrations.

For detailed steps on adding a new provider, refer to the Adding a New Provider guide [1][2].

This should help you integrate Volcengine TOS storage into the project.

To continue talking to Dosu, mention @dosu.

@dosubot[bot] commented on GitHub (Sep 9, 2024): <!-- Answer --> To add Volcengine TOS storage support, you can follow the existing pattern for integrating new storage services. Here are the steps: 1. **Define Environment Variables**: - Add new environment variables for Volcengine TOS similar to the existing ones for S3, Azure Blob, and Aliyun OSS. 2. **Update Configuration**: - Modify the configuration section to include Volcengine TOS as a storage type. 3. **Implement Storage Integration**: - Implement the necessary code to handle file operations (upload, download, delete) using Volcengine TOS SDK. ### Example Configuration Add the following environment variables for Volcengine TOS: ```md - TOS_ENDPOINT: TOS endpoint address - TOS_BUCKET_NAME: TOS bucket name - TOS_ACCESS_KEY: TOS Access Key - TOS_SECRET_KEY: TOS Secret Key - TOS_REGION: TOS region information ``` ### Update Configuration Section Modify the configuration section to include Volcengine TOS: ```md - STORAGE_TYPE Type of storage facility - local (default) - s3 - azure-blob - aliyun-oss - tos # Add this line for Volcengine TOS - TOS_ENDPOINT: TOS endpoint address - TOS_BUCKET_NAME: TOS bucket name - TOS_ACCESS_KEY: TOS Access Key - TOS_SECRET_KEY: TOS Secret Key - TOS_REGION: TOS region information ``` ### Implement Storage Integration Implement the necessary code to handle file operations using the Volcengine TOS SDK. Ensure you follow the same structure as the existing storage integrations. For detailed steps on adding a new provider, refer to the [Adding a New Provider](https://github.com/langgenius/dify-docs/blob/main/en/guides/model-configuration/new-provider.md) guide <sup>[[1]](https://github.com/langgenius/dify-docs/blob/main/en/guides/model-configuration/new-provider.md)</sup><sup>[[2]](https://github.com/langgenius/dify-docs/blob/main/zh_CN/guides/model-configuration/new-provider.md)</sup>. This should help you integrate Volcengine TOS storage into the project. <!-- Dosu Comment Footer --> *To continue talking to [Dosu](https://dosu.dev), mention @dosu.*
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: langgenius/dify-docs-archived#20