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.
33 lines
1.1 KiB
YAML
33 lines
1.1 KiB
YAML
# Builds the Dockerfile at the root for every v* tag and pushes it to this forge's staging registry.
|
|
# IPCR picks it up from there within a minute and publishes it on IPFS; the forge's page then
|
|
# lists the exact `image:` line to use.
|
|
#
|
|
# Differences from a GitHub-hosted workflow, both needed on this forge:
|
|
# images: localhost:5000/… the staging registry (no login, no secret)
|
|
# network=host so buildx's builder can reach that registry
|
|
name: image
|
|
on:
|
|
push:
|
|
tags: ['v*']
|
|
jobs:
|
|
image:
|
|
runs-on: ubuntu-latest
|
|
steps:
|
|
- uses: actions/checkout@v4
|
|
- uses: docker/metadata-action@v5
|
|
id: meta
|
|
with:
|
|
images: localhost:5000/${{ github.repository }}
|
|
tags: |
|
|
type=semver,pattern={{version}}
|
|
type=raw,value=latest
|
|
- uses: docker/setup-buildx-action@v3
|
|
with:
|
|
driver-opts: network=host
|
|
- uses: docker/build-push-action@v6
|
|
with:
|
|
context: .
|
|
push: true
|
|
tags: ${{ steps.meta.outputs.tags }}
|
|
labels: ${{ steps.meta.outputs.labels }}
|