容量管理: zones.rs 直读 nginx file_cache 共享内存记账(双轴: 磁盘 + keys_zone 索引内存), ?scan=1 扫盘上限 20 万文件; POST /api/admin/cache/purge 整区清理(只删文件不删目录, 根治 [crit] mkdir failed); POST /api/admin/cache/invalidate 按制品精准失效(预览->确认两步式, glob/子串, 删除上限 5000/扫描上限 20 万); GET /api/admin/cache 新增 capacity 块; 前端容量面板 + 按制品失效工具条; 测试 test-cache-capacity.sh 48/48(容量 27 + 精准失效 21, 含 EXPECT_MIN 护栏与前端静态契约); docs 容量管理章节
2.3 KiB
2.3 KiB
Contributing Guidelines
The following is a set of guidelines for contributing. We really appreciate that you are considering contributing!
Table Of Contents
Ask a Question
Please ask your question on github using discussions.
Contributing
Report a Bug
To report a bug, open an issue on GitHub with the label bug using the available bug report issue template. Please ensure the issue has not already been reported.
Suggest an Enhancement
To suggest an enhancement, please create an issue on GitHub with the label enhancement using the available feature issue template.
Open a Pull Request
- Fork the repo, create a branch, submit a PR when your changes are tested and ready for review.
- Fill in our pull request template
Note: if you’d like to implement a new feature, please consider creating a feature request issue first to start a discussion about the feature.
Style Guides
Git Style Guide
- Keep a clean, concise and meaningful git commit history on your branch, rebasing locally and squashing before submitting a PR
- Use the Conventional Commits format when writing a commit message, so that changelogs can be automatically generated
- Follow the guidelines of writing a good commit message as described here and summarised in the next few points
- In the subject line, use the present tense ("Add feature" not "Added feature")
- In the subject line, use the imperative mood ("Move cursor to..." not "Moves cursor to...")
- Limit the subject line to 72 characters or less
- Reference issues and pull requests liberally after the subject line
- Add more detailed description in the body of the git message (
git commit -ato give you more space and time in your text editor to write a good message instead ofgit commit -am)
Rust Style Guide
- Rust code should be checked in after
cargo fmthas been run. - The code style broadly complies with the official Rust Style Guide.
- Where feasible, include unit tests.