5 Commits
Author SHA1 Message Date
Worph bef30d8e20 Docs: the forge is the AIO listing only; the split listing is retired (IPCR 1.7.0 is the registry beside a stock Gitea)
ipcr / image (push) Successful in 2m26s
2026-10-12 16:21:23 +00:00
Worph ca8f87050b Split listing support: Gitea and Radicle as separate apps
image / vet (push) Successful in 1m51s
image / image (push) Failing after 29s
- setup: with RUNNER_DIR, fetch the runner registration token from Gitea's
  admin API (POST /admin/actions/runners/registration-token) instead of the
  gitea CLI on Gitea's volume; record secrets/setup-status (ok, unreachable,
  bad-credentials) and exit cleanly when Gitea cannot be used.
- mirror: Radicle is optional. Repositories wait until a node is there (key and
  control socket in RAD_HOME), re-checked every reconcile; RADICLE=off.
- page: /status.json; hide the Radicle parts without a node, banner when Gitea
  is unreachable or refuses the login.
- example workflow: runs-on: ipcr, the forge's own runner label.
- docs: two listings, split (IPCR-Forge) and all in one (IPCR-Forge-AIO).
2026-10-05 16:11:24 +00:00
Worph 13ef14391e Move the store listings to the IPCR app store (Yundera/ipcr Apps/)
Apps/IPCR-Forge, Apps/Gitea and Apps/Radicle live with the rest of the IPCR
app store in the engine repository: the store is built from that folder, and a
link into this submodule would not survive (repository archives leave
submodules out). This repository keeps the forge service, its image and docs.
2026-10-05 14:32:45 +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
Pierre c2d78d8776 Initial commit 2026-10-05 15:16:09 +02:00