Publish
Publish
Where rigs can live, and how to put yours in each place.
A rig artifact is just a .rig.tgz. The interesting question is where it
lives — what does someone install from?
The three places
| Where | Source spec | When to use |
|---|---|---|
| Rig Hub | hub:author/name | Public discovery, public access. Most common. |
| GitHub releases | github:user/repo | Open-source rig with code on GitHub already. No Hub account needed. |
| Local registry | registry:author/name | Private distribution (team, company, air-gapped network). |
You can publish the same rig in multiple places. The artifact is identical; only the resolution path differs.
Pages
- Publish to the Hub —
rig hub publish. - GitHub releases — package as a release asset.
- Local registry — file-based, for private distribution.
- Accounts (
rig login/rig logout) — authenticating with the Hub.
Before you publish
- Pack the artifact.
- Inspect it — read the file list, read the manifest.
- Round-trip test it.
- Confirm
[rig].versionis bumped if you're updating an existing rig. - If the rig is synced (
[sync]is enabled), confirm sync is clean — see Publishing a synced rig.