Worph
98ff2f5783
- bridge/ → forge/, module and binary ipcr-forge, image ghcr.io/yundera/ipcr-forge
(was ipcr-forge-bridge); releases are plain vX.Y.Z tags (workflow image.yml)
- data folders $AppID/bridge/{state,secrets} → $AppID/forge/..., in-container /forge
- docs link to the engine (Yundera/ipcr) instead of relative paths; README
1.6 KiB
1.6 KiB
IPCR Forge
A self-hosted forge whose releases live on IPFS: work in Gitea as usual, its Actions build your images, the IPCR engine publishes them under one IPNS name (and your ENS or DNS name), and every public repository is mirrored to Radicle.
git push origin v1.0.0
docker pull ipcr.localhost:4767/ipns/metadec.eth/ipcr-hello:1.0.0 # any host running IPCR
docker pull ipcr-<domain>/ipns/metadec.eth/ipcr-hello:1.0.0 # anywhere, through the forge
This repository is the add-on; Yundera/ipcr is the engine (the
registry gateway, IPFS import, IPNS naming and admin API), used here as the image
ghcr.io/yundera/ipcr.
- docs/forge.md: how it works, the trust model, findings, what was verified.
- Apps/IPCR-Forge/: the Yundera AppStore listing (compose, rationale, seed).
- forge/: the forge service,
ghcr.io/yundera/ipcr-forge(Go, standard library only): the Gitea → Radicle mirror, the forge's page and admin pages (Gitea login), the staging registry's gate and per-repository push credentials, and the install step. - Apps/Gitea/, Apps/Radicle/: the standalone listings the forge is built from.
Develop
cd forge && go vet ./... && go test ./...
docker build -t ghcr.io/yundera/ipcr-forge:dev forge
Releases: a vX.Y.Z tag publishes ghcr.io/yundera/ipcr-forge:X.Y.Z
(.github/workflows/image.yml). The listing pins both images: this
one and the engine's.