feat: add S3 file storage support (#1688)

This commit is contained in:
Weijie Zhao
2025-11-06 15:37:04 +08:00
committed by GitHub
parent 08525bcb4b
commit bc1368abcc
10 changed files with 505 additions and 9 deletions

View File

@@ -484,6 +484,47 @@
"key": "maxsize",
"default_value": "20MB",
"comment": "The maximum size of a file, as a human-readable string.\nWarning: The max size is limited 2^64-1 bytes due to the underlying datatype"
},
{
"key": "type",
"default_value": "local",
"comment": "The type of file storage backend. Supported values are `local` and `s3`."
},
{
"key": "s3",
"comment": "Configuration for S3 storage backend",
"children": [
{
"key": "endpoint",
"default_value": "",
"comment": "The S3 endpoint to use. Can be used with S3-compatible services like MinIO or Backblaze B2."
},
{
"key": "bucket",
"default_value": "",
"comment": "The name of the S3 bucket to store files in."
},
{
"key": "region",
"default_value": "",
"comment": "The S3 region where the bucket is located."
},
{
"key": "accesskey",
"default_value": "",
"comment": "The S3 access key ID."
},
{
"key": "secretkey",
"default_value": "",
"comment": "The S3 secret access key."
},
{
"key": "usepathstyle",
"default_value": "false",
"comment": "Whether to use path-style addressing (e.g., https://s3.amazonaws.com/bucket/key) instead of virtual-hosted-style (e.g., https://bucket.s3.amazonaws.com/key). This is commonly needed for self-hosted S3-compatible services. Some providers only support one style or the other."
}
]
}
]
},