Registries
The platform runs four artifact registries, one per package ecosystem. Your tools publish to and pull from them with credentials provisioned at login.
| Registry | Host | Holds |
|---|---|---|
put |
put.putnami.dev |
Putnami-native packages (config, migrations, archives, site content) |
npm |
npm.putnami.dev |
npm packages |
go |
go.putnami.dev |
Go modules |
oci |
oci.putnami.dev |
OCI images |
Credentials are set up automatically by putnami cloud login;
you rarely touch them directly.
Credentials
| Want to… | Do this |
|---|---|
| Set up / show per-registry tokens | putnami cloud registries |
| Mint a bearer for one registry | putnami cloud token --for npm|go|oci|registry |
| Resolve a token by host | putnami cloud registry-token --host <host> |
| Revoke and remove tokens | putnami cloud logout |
Publishing
Most publishing happens as part of putnami publish and putnami deploy. The
Putnami-native (put) registry also has direct publishers:
| Publish… | Command |
|---|---|
| Config schema + values | putnami cloud publish-config |
| Migration bundle | putnami cloud publish-migration |
| Pre-built archives | putnami cloud publish-archives |
| Docs (site-content bundle) | putnami cloud publish-doc |
OCI images
The OCI registry can copy and retag images server-side, without pulling and re-pushing layers:
| Want to… | Do this |
|---|---|
| Copy an image between repos | putnami cloud oci copy <src-ref> <dst-ref> |
| Add tags to an existing digest | putnami cloud oci retag <ref> <tag…> |
Refs are registry-relative (ns/name, ns/name:tag, or ns/name@sha256:…).
Both verbs are pure metadata within the shared content-addressed store — zero
blob bytes move — and a multi-arch image index is copied whole (every platform
manifest comes along). Credentials come from the registry token seam (the same
one cloud login provisions), never from provider credentials.
Availability
| Page | Status |
|---|---|
Putnami packages (put) |
Planned |
| npm registry | Planned |
| Go module proxy | Planned |
| OCI images | Available: copy and retag are documented above |