ipcr/ipcr-forge
3
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity
24 Commits 1 Branch 7 Tags
main
Commit Graph
3 Commits
Author SHA1 Message Date
Worph eb80042f13 CI: build on every push, so release tags build
image / vet (push) Successful in 1m35s
Details
image / image (push) Failing after 37s
Details 
The push trigger's paths filter also applied to tag pushes, which change no
files: the v0.4.0 tag started no run and ghcr.io/yundera/ipcr-forge:0.4.0 was
never published (a fresh install failed pulling it).
 2026-10-05 15:11:11 +00:00
Worph 98ff2f5783 Rename the bridge to the forge service; this repository is the add-on 
- 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
 2026-10-05 13:21:11 +00:00
Worph 6fe4c40cbe IPCR Forge v3: Gitea as the source of truth, public repos mirrored to Radicle 
Users found Radicle-as-source unfriendly (v1, v2). Gitea is now where
people work; its Actions build images into the staging registry IPCR
follows, as in v2.

- bridge/: ipcr-forge-bridge (Go). Install step mints a public-only
  token, registers one system webhook and creates the ipcr-hello example;
  the service mirrors every public repo one way to Radicle (rad init,
  canonical tags rule, git push rad) and serves the forge's page.
- Compose: gitea + act_runner on a separate dind; tile opens Gitea;
  tips link the forge page.
- Removed the Radicle CI broker (ci/) and the nginx landing page.
 2026-10-04 18:34:26 +00:00