IPCR Forge admin
Publisher name
Key
- Key
…- IPNS name
…- Pull as
…
Every image is published under this one name. Back the key up (Key backup tab): it exists only on this server.
Your domain or ENS name
Point a name you own at the IPNS name, then enter it here. Once it checks out, pull lines use it.
How to point it here
ENS: in the ENS manager, Records → Content hash =
ipns://k51…DNS: a TXT record _dnslink.example.com =
dnslink=/ipns/k51…Public pulls
This forge's images, and only those, can also be pulled from any machine with plain Docker, without IPCR,
through ipcr-…. Read-only; a pull there pins nothing. Layers are still checked by digest.
docker pull …Health
IPNS record
The record must be renewed by this node while it is online (Kubo does it every 4 h). Lifetime is how long a record stays valid if this node goes offline; TTL is how long resolvers cache it.
Storage
Published images are pinned and never collected. Unpublishing an image frees the blocks no other image uses.
Node
Listening on
Published images
Every tag can be pulled three ways: by IPFS CID (this exact image, forever), by IPNS name (follows the tag), and by your ENS or DNS name once it checks out (Overview).
Root organisation
The public repositories of this Gitea organisation are also published at the root of the forge's
name: metadec/app → …/ipns/<name>/app. Its members (Gitea teams) are the ones who
can publish there. Leave empty for none.
Which repositories may publish
Each public repository switched on here publishes under its own name only: the forge sets an
IPCR_PUSH_TOKEN secret on it, and the staging registry accepts that token for that name and no other.
Workflows log in with it (see the forge page's template). New public repositories are on.
Key backup
Download a backup
The key, encrypted with your passphrase (at least 12 characters). Keep the file and the passphrase apart. Without a backup, losing this server loses the name for good.
Restore a backup
Makes the backed-up key this forge's publisher key: to move a forge to a new server, or recover one. The current key is kept (renamed), not deleted.
Every image name then points at this server's images under the restored name. On a fresh server, the name's last published images are adopted.