rajames/LithosAnanke
1
1
Fork 0
Code Issues 43 Pull Requests 1 Actions 1 Packages Projects Releases Activity

ci: faster CI (#119, #120); the Try-it page in the .com style #122

Open
rajames wants to merge 3 commits from StarForth-v4.0.0 into master
pull from: StarForth-v4.0.0
merge into: :master
Conversation 0 Commits 3 Files Changed 7
+137 -29
3 Commits
Author SHA1 Message Date
rajames 7be2047aee Merge master into StarForth-v4.0.0: #118's merge commit, so the next PR is up to date
Build / Image RASPI (push) Successful in 4m24s
Details
Build / Image PC (push) Successful in 4m28s
Details
Build / Image MILKV (push) Successful in 4m28s
Details
Build / v4 tests (32- and 64-bit cells) (push) Successful in 11m23s
Details
Acceptance / Acceptance (pull_request) In progress
Details 
master's only commit not on the branch is the merge of #118, whose tree is the branch's own
4f6a267b.
 2026-11-06 21:44:17 +00:00
rajamesandClaude Opus 5.5 475dac67ef demo: "Try it" is its own page on the .com, in the landing page's style (#117) 
Captain Bob, 2026-11-06: "I want the try it as it's very own page and
use the landing page we designed earlier ... as a baseline."

The landing page is the .com's Main.WebHome. The Try-it page follows
it: a floating box -- Your Machine, in place of Quick Facts -- a linked
title, == sections, {{info}} and {{warning}}. It goes at TryIt on the
.com (/bin/view/TryIt/), with the console embedded and links back to
the landing page and the source.

The page is on the .com now, so apache-demo.conf lets the .com frame
the console (frame-ancestors), and the demo's host is
try.starshipos-f18.com.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01GE3SDvQn5EoxdGufk84zz2
 2026-11-06 20:47:35 +00:00
rajamesandClaude Opus 5.5 672d275f5c ci: no quick check on master after a merge (#119); the runner image's recipe (#120) 
Captain Bob, 2026-11-06: a small server, a little sluggish. Each change
cost about an hour of runner time; the gate itself is about 15 minutes.

#119 -- build.yml runs on pushes to the working branch only. What
reaches master arrives through a PR whose content just passed
acceptance; checking it again cost ~23 minutes after every merge.

#120, first step -- ci/runner-image/Dockerfile: gitea/runner-images'
Ubuntu 24.04 (with Node, for the actions) plus what
make ARCH=amd64,aarch64,riscv64 init INIT_DOCS=0 installs -- run from
the Makefile itself, not a copied list -- and Maven for publishing.
.gitea/workflows/runner-image.yml builds it and publishes it to the
package registry as lithosananke-runner:<commit>. The workflows switch
to it in a later change, once it is published and has passed
acceptance. It needs the runner to lend jobs its Docker daemon
(container.docker_host: automount) and a PACKAGES_TOKEN secret, unless
the Actions token may publish packages.

make init does git lfs install --local only inside a checkout: the
image build is not one.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01GE3SDvQn5EoxdGufk84zz2
 2026-11-06 20:43:42 +00:00