OpenListTeam / OpenListTeam/OpenList
[Feature] 原版的几个不合理设计（Docker、API接口、S3）
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 24.7k
- Forks
- 2.3k
- Avg merge
- 1d 20h
- Merged PRs (30d)
- 36
Description
关于Docker使用方式标准化，API接口变更，用户UpSert接口，S3兼容性和必要性。
-
支持环境变量配置Docker中部分参数如用户信息不通过自动生成而是读取环境变量等。
在不需要持久卷的使用场景，环境变量更容易迁移服务器部署
一套helm配置文件,多个节点可以确保一致性 -
API接口，一旦固定，不要随意改变
/api/admin/storage/create
/api/admin/storage/update
这两个接口不够需要增加语义化upsert接口
并规范各API接口统一性 -
支持并发请求三方网盘拉平tree结构，不通过缓存等直接请求对应文件。并考虑拉取速率。
And see https://github.com/OpenListTeam/OpenList/issues/74#issuecomment-2973235964
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing the issue and its referenced comment, then inspect the Docker and Helm deployment configuration and the handlers for /api/admin/storage/create and /api/admin/storage/update. Because the request combines deployment settings, API design, concurrent cloud-drive access, and S3 compatibility, define and split the scope into focused acceptance criteria before implementation.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, go, helm
- Domain
- backend-api-design, cloud, devops
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100