ci/woodpecker/push/main-amd64-build Pipeline was successful
Agent, Probe and Backend now start from one static compose.yaml plus a local
.env: the panel (or the release assets, for the very first Backend) provides
the file, the panel's command writes the public values into .env, checks the
file's SHA-256 and runs compose up. Updating is compose pull && compose up -d.
The image is chosen by the CI channel (:latest, or MOSHIRO_VERSION in .env),
not by the panel; the previous one-line script stays as a fallback.
- packaging/compose/{agent,probe,backend}/compose.yaml are the single source,
embedded in the Backend and served at /install/compose/{file}; the root
compose.yaml moved there. Releases also carry them and list them in the
signed SHA256SUMS.
- The container entrypoint defaults the node name to the host name.
- Join token creation returns a compose block (.env, url, hash, per-platform
commands); the admin dialog leads with it.
- Remove code with no references (HotLayer members, LiveHub.SubscriberCount,
QueryService.ParseParams, ReleaseService.Forget, a few constants) and reduce
the install-code lookup to the role it is for.
文档
按类别组织。每份文档开头写明它是已实现的说明还是设计稿;对不上代码时以代码为准。
| 类别 | 文档 | 内容 |
|---|---|---|
| 设计 | architecture.md | 架构、数据链路、安全边界、设计决策 |
| protocol.md | 线协议、方法的方向与角色 | |
| storage.md、query.md | 存储;展示数据查询 | |
| measurement.md、analysis.md | 采集引擎与任务模型;分析层与指标 | |
| 安全 | security.md | 零信任:威胁模型、缺口与状态、协议卡口、监听隐身、extension |
| access.md | 访问控制与入网信任链:能力、API key、passkey、操作员集合、属主、安装的供应链 | |
| enrollment.md | 注册与身份:Agent、Probe 的接入,节点本地硬上限 | |
| 接口 | api.md、api-guidelines.md | 端点说明;API 规范与约束 |
| 运维 | deployment.md | 构建、发布、CI、部署与更新、发布密钥 |
| 开发 | project-layout.md、coding-style.md | 仓库结构与依赖规则;代码风格 |