See ROADMAP.md → good first issues.
What / 要做什么
The repo now has a Dockerfile that starts one node joining the live network. Locally, the normal dev workflow is two peered nodes on one machine (corepack pnpm dev:node1 + corepack pnpm dev:node2, see package.json).
仓库现在有一个 Dockerfile,起一个接入实网的节点。本地开发的常规方式是同机两个互联节点(corepack pnpm dev:node1 + dev:node2,见 package.json)。
Add a docker-compose.yml that starts two containers built from the same Dockerfile, peered with each other instead of the live seed (mirroring dev:node1/dev:node2's --p2p-port/--peers flags), with a named volume per node so chain data persists across restarts. Document it in the README's Docker section.
Why this is a good first issue
Contained to Docker/compose config — no TypeScript required. Good way to learn how the CLI's start flags (--p2p-port, --peers, --api-port) work.
Scope
New docker-compose.yml + a short README addition. Don't change the Dockerfile itself unless something in it blocks this (flag it in the PR if so).
See ROADMAP.md → good first issues.
What / 要做什么
The repo now has a
Dockerfilethat starts one node joining the live network. Locally, the normal dev workflow is two peered nodes on one machine (corepack pnpm dev:node1+corepack pnpm dev:node2, seepackage.json).仓库现在有一个
Dockerfile,起一个接入实网的节点。本地开发的常规方式是同机两个互联节点(corepack pnpm dev:node1+dev:node2,见package.json)。Add a
docker-compose.ymlthat starts two containers built from the sameDockerfile, peered with each other instead of the live seed (mirroringdev:node1/dev:node2's--p2p-port/--peersflags), with a named volume per node so chain data persists across restarts. Document it in the README's Docker section.Why this is a good first issue
Contained to Docker/compose config — no TypeScript required. Good way to learn how the CLI's
startflags (--p2p-port,--peers,--api-port) work.Scope
New
docker-compose.yml+ a short README addition. Don't change theDockerfileitself unless something in it blocks this (flag it in the PR if so).