3 Commits

Include renames

Author	SHA1	Message	Date
justme	bac1c27e72	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
justme	12be44645f	feat: install nodes and the backend from a static compose file; remove dead code [CI] ... 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.	2026-10-08 20:24:23 +08:00
justme	e014a19554	docs: reorganize into design, security, api, ops and dev; drop stale designs; refresh the diagrams [CI] ... - Group docs by category with an index (docs/README.md); fix every link, code comment and the protocol conformance test that read docs/protocol.md. - access.md and security.md rewritten to what is implemented: removed the unadopted member-proof chain, roles and recovery key that do not exist, the old implementation order and the budgets; gaps now carry a status. - enrollment, deployment, api: the install flow is the static, hash-checked script with environment variables; no default admin. - README and architecture: new topology and update-flow diagrams (operator passkey, CI signing, registry feed, auth and trust modules).	2026-10-08 19:37:56 +08:00