From a8a3037cbaedb126bee1940b21a28b864a2254a0 Mon Sep 17 00:00:00 2001 From: Worph Date: Sun, 4 Oct 2026 10:36:11 +0000 Subject: [PATCH] IPCR Forge page: fix the publish guide after a run-through MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Following the page end to end on a fresh demo box found four gaps: - rad init needs a Git repository with a commit: show git init/add/commit - the node must be running: rad node start - rad seed ends with "✗ Target not met" from the public seeds; harmless, check the Radicle explorer instead - the first build takes 5-10 min while the runner pulls its images Also say to commit the workflow before tagging. --- Apps/IPCR-Forge/seed/site/index.html | 25 ++++++++++++++++++------- 1 file changed, 18 insertions(+), 7 deletions(-) diff --git a/Apps/IPCR-Forge/seed/site/index.html b/Apps/IPCR-Forge/seed/site/index.html index 1f63f92..f877ca2 100644 --- a/Apps/IPCR-Forge/seed/site/index.html +++ b/Apps/IPCR-Forge/seed/site/index.html @@ -98,8 +98,9 @@ service. Code lives on Radicle, Gitea Actions builds it, and IPCR serves the ima
→
5 · Pullany server with IPCR: ipcr.localhost:4767/ipns/…
-

Steps 2 to 4 are automatic and take two to three minutes. A repository needs no configuration -beyond committing a workflow.

+

Steps 2 to 4 are automatic and usually take a few minutes. The very first build on this server +takes longer (about 5 to 10 minutes) while the runner downloads its build images. A repository +needs no configuration beyond committing a workflow.

Published images

Loading…

@@ -107,17 +108,26 @@ beyond committing a workflow.

Publish a project

  1. Install Radicle on your machine and create an identity: see - radicle.xyz, then rad auth.
    2. + radicle.xyz, then rad auth. + Start your own node, which carries your pushes: rad node start.
  2. Connect to this server's node so your pushes reach it: 
    rad node connect <node-id>@<this server>:8776
    3. -
  3. Publish the repository from its folder: rad init. It prints a repository - ID (rad:z…).
    4. +
  4. Publish the repository. It has to be a Git repository with at least one commit: +
    git init -b main
+git add -A
+git commit -m "First commit"
+rad init
    + rad init prints the repository ID (rad:z…).
  5. Let this node seed it. The node only keeps repositories it is told to (seeding policy block). In this server's Terminal app or over SSH: - 
    docker exec radicle-node rad seed rad:z… --scope all
    6. + 
    docker exec radicle-node rad seed rad:z… --scope all
    + It ends with ✗ Target not met: could not fetch from […]. That is about the public + Radicle seeds, not this server, and can be ignored. The repository is in place once it shows + in the Radicle explorer.
  6. Add a workflow at .gitea/workflows/build.yml. This one builds the Dockerfile at the root and publishes it for every v* tag. The - REGISTRY_TOKEN secret is already set for every repository. + REGISTRY_TOKEN secret is already set for every repository. Commit it + (git add .gitea && git commit -m "Build the image"). 
    on:
   push:
     tags: ['v*']
@@ -211,6 +221,7 @@ for IPFS peers. Details: