rune pack

Package a runeset directory into a distributable .runeset.tgz archive.

rune pack <runeset-dir> [flags]

Examples

# Package with default name (<dir>.runeset.tgz)
rune pack ./my-app
 
# Custom output path
rune pack ./my-app -o dist/my-app-1.2.0.runeset.tgz
 
# Also write a SHA-256 checksum file
rune pack ./my-app -o dist/my-app-1.2.0.runeset.tgz --sha256

Outputs:

<output>.runeset.tgz — the bundle.
<output>.runeset.tgz.sha256 — checksum, if --sha256.

Flags

Flag	Notes
`-o, --output`	Output path. Defaults to `<dir>.runeset.tgz`.
`--sha256`	Also write a `.sha256` file alongside the archive.

What goes in

pack validates that the directory has a runeset.yaml and a casts/ directory, then archives everything in it:

runeset.yaml (required).
casts/ (required).
values/, templates/, README.md and anything else present.

There is no ignore mechanism — local files you don't want shipped (a secrets.local.yaml, .git, node_modules) must live outside the runeset directory.

Distributing

After packing you can:

Upload to a release page or CDN.
Push to a private bucket and reference by URL.
Commit to a git repo and use rune cast github.com/org/repo@tag.