Clarify local runtime bundle bootstrap
Stop presenting make runtime-bundle as a turnkey fresh-checkout bootstrap\nwhen the checked-in manifest is intentionally empty. The manifest comments,\nruntimebundle error messages, Make help, README, and AGENTS docs now all\ndescribe the same local-first flow: stage an archive, use a separate local\nmanifest copy with url/sha256, then bootstrap ./runtime from that manifest.\n\nKeep the existing package/fetch commands intact, and add a small runtimebundle\nregression test so the local-manifest guidance does not drift again.\n\nValidated with make help and GOCACHE=/tmp/banger-gocache go test\n./internal/runtimebundle.
This commit is contained in:
parent
ccba07ec68
commit
617f677c9b
6 changed files with 66 additions and 17 deletions
|
|
@ -9,7 +9,7 @@
|
|||
|
||||
## Build, Test, and Development Commands
|
||||
- `make build` builds `./banger` and `./bangerd`.
|
||||
- `make runtime-bundle` bootstraps `./runtime/` from `runtime-bundle.toml`.
|
||||
- `make runtime-bundle` bootstraps `./runtime/` from the archive referenced by `RUNTIME_MANIFEST`; the checked-in `runtime-bundle.toml` is only a template.
|
||||
- `banger` validates required host tools per command and reports actionable missing-tool errors; do not assume one workstation's package set.
|
||||
- `./banger vm create --name testbox` creates and starts a VM.
|
||||
- `./banger vm ssh testbox` connects to a running guest.
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue