Files
MoShiro/docs
justme bac1c27e72
ci/woodpecker/push/main-amd64-build Pipeline was successful
fix: compose passes .env through env_file; clearer name and channel messages [CI]
podman-compose does not substitute defaults inside "environment:" (a value
like ${MOSHIRO_NAME:-} reached the node as the literal text), so the node was
enrolled with an invalid name and reported the wrong network scope. The three
compose files now read .env with env_file and only interpolate image and
network_mode; the Backend .env keys are the container's own names
(MoShiro__PublicUrl, MoShiro__ClaimCode).

- The generated .env no longer carries a comment line for MOSHIRO_NAME; the
  dialog says how to choose a name instead.
- The container entrypoint prints the name it enrolls with and defaults
  MOSHIRO_NETWORK_SCOPE to host (Docker Desktop sets container in .env).
- The overview and line pages say "measurement channel not established"
  instead of "not connected": the agent can be reachable and pingable while
  the measurement TCP/UDP path is not.
2026-10-08 20:47:38 +08:00
..

文档

按类别组织。每份文档开头写明它是已实现的说明还是设计稿;对不上代码时以代码为准。

类别 文档 内容
设计 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 仓库结构与依赖规则;代码风格

各子项目的说明在它们自己的目录里:backend、fleet、agent、probe、web。