You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
cluster: make example presets build-from-local, add gravity_cli Makefile target
Two ergonomics fixes discovered while following the cluster deployment
docs end-to-end on a fresh machine:
1. Every cluster.toml under cluster/example/ ships with
source = { github = "Galxe/gravity-sdk", rev = "main" }
This instructs deploy.sh to re-clone gravity-sdk and cargo-build it a
second time inside the runtime dir, even when the user has already
built the binaries in target/quick-release from the top-level Makefile.
The result is a long re-build, extra disk usage, and ENOSPC on
machines with modest free space.
Change all five examples to source = { project_path = "../" }, matching
cluster/cluster.toml.example and what the presets were clearly intended
to be used for (the 1_node preset is literally named gravity-devnet-one).
Anyone wanting github-source deploys can still flip the line back.
2. The top-level Makefile had targets for gravity_node / bench / kvstore
but none for gravity_cli — yet init.sh, genesis.sh, and deploy.sh all
require gravity_cli and fail with "gravity_cli not found! Please build
it first." So the cluster docs instruction of "make BINARY=gravity_node
MODE=quick-release" does not actually produce a working setup.
Add a gravity_cli target, and a cluster convenience target that builds
both gravity_node and gravity_cli in one invocation. The cluster docs
can now say `make cluster MODE=quick-release` and work out of the box.
Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
0 commit comments