OpenListTeam / OpenListTeam/OpenList
[Feature] 新增api - 备份/还原
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 24.7k
- Forks
- 2.3k
- Avg merge
- 1d 20h
- Merged PRs (30d)
- 36
Description
Please make sure of the following things
- I have read the documentation.
- I'm sure there are no duplicate issues or discussions.
- I'm sure this feature is not implemented.
- I'm sure it's a reasonable and popular requirement.
Description of the feature / 需求描述
截至4.0.3版本为止,目前可以在web端 /@manage/backup-restore 页面进行手动备份恢复。
简单看了下逻辑是拼接了以下四个接口的data。
- /api/admin/setting/list
- /api/admin/user/list
- /api/admin/storage/list
- /api/admin/meta/list
当需要流程化自动备份时,虽然可以手动完成这部分工作,但是无法应对未来接口的变化。
例如
- 备份流程中新增了其他内容
- api接口的变更
Suggested solution / 实现思路
希望新增一个 备份/还原 接口来隐藏 备份/还原 操作的细节。
/api/admin/backup
/api/admin/restore
web ui中的备份还原操作也转而调用该接口,隐藏当前备份还原的细节。
Additional context / 附件
No response
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 at the web UI page /@manage/backup-restore and trace its use of /api/admin/setting/list, /api/admin/user/list, /api/admin/storage/list, and /api/admin/meta/list. Define the /api/admin/backup and /api/admin/restore entry points, then update the UI to use them while preserving the current backup and restore contents and behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- api, backend
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100