Peering: admin console visibility for peers, feeds, spend and held invoices
维护者通常 1 天内回复
还没有人认领这个 Issue。
评估
- 难度
- 5/5
- 预计耗时
- 一周以上
- 新手友好度
- 28/100
- Issue 类型
- 功能
- 描述清晰度
- 基本清楚
- 活跃度
- 活跃
- 技术栈
- typescript
- 领域
- backend
调研方向
Start with the relay peering work in #931 and the existing admin operations console panels for mirrors and workers; follow their bounded data access and admin authentication and rate-limit patterns. The scope covers peer configuration, feed health, per-peer invoices and budgets, and actionable held invoices, with budget and invoice events visible in the console. Done means an operator can answer the stated peering and spending questions there, and approving a held invoice pays it and activates its feed.
由索引模型根据 Issue 内容生成。
描述
Part of the relay peering work in #931.
Scope
Operator visibility for peering, alongside the existing mirror/worker panels in the admin operations console:
- Configured peers: pubkey, endpoint, terms, relationship state (active / suspended / lapsed).
- Feed health per peer: last sync/reconciliation, live-feed status, events served via feed vs on-demand requests.
- Money per peer per period: invoices received, paid, held; budget remaining; held invoices actionable (approve → pay manually, or reject).
- Budget-exhaustion and held-invoice events are visible without reading logs.
Follows the existing ops-console patterns for data access (bounded queries, same admin auth/rate-limit chain).
Acceptance
- An operator can answer "who are we peering with, what has it cost this period, and is anything waiting on me?" from the console alone.
- Approving a held invoice from the console pays it and activates the corresponding feed.
- 主要语言
- TypeScript
- 星标
- 829
- 派生
- 234
- 平均合并
- 17 小时 6 分钟
- 30 天内合并 PR
- 92
环境准备
- 提供 Dockerfile 或 Docker Compose 文件
- 有 Pull Request 模板
- 阅读贡献指南
从这里开始
- 先读完整个 Issue，再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库，在一个分支上完成修改。
- 提交 Pull Request，并在描述里引用这个 Issue 编号。
cameri/nostream 的其他 Issue
-
factory rewrite rust
难度 2/5 1-3 小时 新手友好度 68/100
维护者通常 1 天内回复
-
factory rewrite rust
难度 2/5 1-3 小时 新手友好度 78/100
维护者通常 1 天内回复
-
test: user-subscription specs fail outside UTC, so the pre-commit hook cannot pass可能已有人在做 @tejasvasingh2004 今天认领。 未关闭
难度 2/5 1-3 小时 新手友好度 78/100
维护者通常 1 天内回复
-
bug factory rewrite rust
难度 2/5 1-3 小时 新手友好度 78/100
维护者通常 1 天内回复
-
bug factory rewrite rust
难度 2/5 1-3 小时 新手友好度 84/100
维护者通常 1 天内回复
相似的 Issue
-
a10y a10y-audit ai-driven-qa claude
难度 2/5 1-3 小时 新手友好度 86/100
linagora/twake-directory-manager#219 ·
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 68/100
维护者通常 1 天内回复
-
type: bug
难度 2/5 1-3 小时 新手友好度 79/100
维护者通常 1 天内回复
-
0️⃣ phase/new
难度 2/5 1-3 小时 新手友好度 82/100
维护者通常 1 天内回复
-
Pulse v7: buildPreferencesFromTelos() bypasses telosSectionOrFile(), renders empty on unified-TELOS installs可能已有人在做 @zephyr91 今天认领。 未关闭
难度 2/5 1-3 小时 新手友好度 75/100
danielmiessler/LifeOS#2393 ·
维护者通常 4 天内回复