Outcome
Give Hyperpush a truthful, repeatable Docker-first deployment baseline on a generic VM with Mesh clustering that works without repo-local magic.
Scope
- Generic Docker-on-a-VM deployment path for Mesh clustered apps
- Node identity, discovery, clustering, and bootstrap UX must be stable enough for Hyperpush
- Container/runtime contract should be simple enough to document and automate
- Close the gap between "language supports clustering" and "operator can actually deploy this product"
Acceptance criteria
- A generic VM + Docker path exists and is documented
- The clustered runtime starts, discovers peers, and stays healthy under the Hyperpush shape
- The deploy path is truthful for both single-node and clustered product deployments
- Any required env/entrypoint/runtime assumptions are explicit and tested
Roadmap notes
- Domain: Mesh
- Track: Mesh Foundation
- Commitment: Committed
- Critical path: 1
Detailed acceptance criteria
- Generic Docker-on-a-VM cluster bootstrap is documented and repeatable.
- Peer discovery, identity, and health verification work without repo-local magic.
- Single-node and clustered product deployments are both truthful.
Initial sub-issues
Outcome
Give Hyperpush a truthful, repeatable Docker-first deployment baseline on a generic VM with Mesh clustering that works without repo-local magic.
Scope
Acceptance criteria
Roadmap notes
Detailed acceptance criteria
Initial sub-issues