irisandClaude Opus 5
f842d0e512
READ BEFORE PULLING. A Managed component's service unit is named <config key>-<component name>, so this rename moves the unit from ai-app-backend to ai-app-server and nothing points at the old one afterwards. Uninstall the backend component from its card *first*, while it is still called "backend"; then pull, accept the new declaration -- .dev-updater.ron is a request, so the card shows it as pending -- and build. The unit installs under the new name. Two things reset rather than break, both keyed by component name: the per-component built_from sha, and the build and runtime logs. One build makes the sha current again. Also drops the claim that the components list is walked in order. They have built in parallel since 2026-08-28, so the reasoning the comment gave -- backend first, so a failing APK leaves the phone what it had -- no longer describes what happens. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01VETa8afmpWaYezLCqJhDB8
42 lines
1.9 KiB
Plaintext
42 lines
1.9 KiB
Plaintext
// Read by Dev Updater. Structured as the body of the config: no outer
|
|
// parentheses, so nothing here is indented for the sake of a wrapper.
|
|
//
|
|
// This file sits at the checkout root because the project Dev Updater
|
|
// serves is the whole repository -- one checkout producing two things.
|
|
// Each component says where it lives with `cwd`, relative to this
|
|
// directory, rather than one of them reaching out of the other with `../`.
|
|
|
|
// What to call this project before there is a build to read a label from.
|
|
// A built APK wins: it is the authority on what will actually install.
|
|
label: "AI Sessions",
|
|
|
|
// The two halves this checkout produces: the server a phone talks to, and
|
|
// the app that talks to it. They are built in parallel -- this list is the
|
|
// set, not a sequence, so nothing here should be read as an order.
|
|
components: [
|
|
Server(
|
|
name: "server",
|
|
build: "cargo build --release",
|
|
cwd: "server",
|
|
// Dev Updater's own built-in service implementation, generated
|
|
// into its data directory and driven through the same interface a
|
|
// project-supplied script would be. ai-app carried a script of its
|
|
// own until 2026-08-28; it ran `target/release/ai-server` with no
|
|
// arguments and no environment, which is the generic case exactly,
|
|
// so it was two copies of one thing and the copy that could not be
|
|
// tested from here -- the OpenRC branch -- was duplicated with it.
|
|
//
|
|
// Resolved against this component's `cwd`, so this is
|
|
// `server/target/release/ai-server`.
|
|
service: Managed("target/release/ai-server"),
|
|
),
|
|
Apk(
|
|
name: "app",
|
|
// Resolved against this directory, and run in `app/` -- the script
|
|
// cds to its own directory anyway, so the cwd is here to say where
|
|
// the app is rather than because the build needs it.
|
|
build: "app/build-apk.sh",
|
|
cwd: "app",
|
|
),
|
|
],
|