Daniel Maksymilian Syrnicki
f0acc4427e
Slice 2 of the self-update story. Tagging a release on main now produces a downloadable self-update payload on the Forgejo releases page, and a running box can pull it down, verify it, atomically swap to the new version, and health-check the result. New pieces: - scripts/build-release-tarball.sh <version> — packages the furtka/ package + bundled apps/ + a root-level VERSION file as dist/furtka-<version>.tar.gz, plus a .sha256 sidecar and a release.json metadata blob. - scripts/publish-release.sh <version> — uses the Forgejo v1 API to create a release (body pulled from the CHANGELOG section for this tag, pre-release auto-flagged on -alpha/-beta/-rc) and upload the three assets sequentially. Needs \$FORGEJO_TOKEN. - .forgejo/workflows/release.yml — tag-triggered, runs both scripts with the new \$FORGEJO_RELEASE_TOKEN repo secret. - furtka/updater.py — check_update, prepare_update, apply_update, run_update, rollback. Atomic symlink swap, sha256 verify (TOCTOU- safe: re-hashes on-disk file), health-check post-restart with auto-rollback on failure, stage-by-stage progress persisted to /var/lib/furtka/update-state.json so the UI can poll independent of the (restarting) API process. Path overrides via FURTKA_ROOT / FURTKA_STATE_DIR / FURTKA_LOCK_PATH so tests pin a tmpdir. - furtka/cli.py — \`furtka update [--check] [--json]\` and \`furtka rollback\`. - tests/test_updater.py — 15 tests: version compare, sha256 verify, tarball extract (including traversal refusal), lockfile, apply happy + rollback paths, rollback CLI, check_update with stubbed Forgejo. - iso/build.sh — writes VERSION at the tarball root so the install path matches the self-update path (previously assumed only the release script did this). RELEASING.md now points at the automated flow — no more manually clicking "Create release" on the Forgejo UI. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
111 lines
5 KiB
Bash
Executable file
111 lines
5 KiB
Bash
Executable file
#!/usr/bin/env bash
|
|
# Build a Furtka live ISO.
|
|
#
|
|
# From the repo root or from iso/ on any host with Docker:
|
|
# ./iso/build.sh
|
|
#
|
|
# The build runs inside a privileged `archlinux:latest` container because
|
|
# mkarchiso needs root + loop mounts + an Arch package manager, which
|
|
# Ubuntu doesn't provide natively. Output ISO goes to iso/out/.
|
|
set -euo pipefail
|
|
|
|
SCRIPT_DIR="$(cd "$(dirname "${BASH_SOURCE[0]}")" && pwd)"
|
|
REPO_ROOT="$(cd "$SCRIPT_DIR/.." && pwd)"
|
|
OUT_DIR="$SCRIPT_DIR/out"
|
|
|
|
if [[ "${FURTKA_ISO_INNER:-0}" != "1" ]]; then
|
|
mkdir -p "$OUT_DIR"
|
|
echo "==> Launching build container"
|
|
exec docker run --rm --privileged \
|
|
-v "$REPO_ROOT:/work" \
|
|
-w /work \
|
|
-e FURTKA_ISO_INNER=1 \
|
|
archlinux:latest \
|
|
bash /work/iso/build.sh
|
|
fi
|
|
|
|
# ---- inside the container from here on ----
|
|
|
|
echo "==> Syncing pacman, installing archiso"
|
|
pacman -Syu --noconfirm --needed archiso
|
|
|
|
PROFILE_SRC="/usr/share/archiso/configs/releng"
|
|
PROFILE_WORK="/tmp/furtka-profile"
|
|
BUILD_WORK="/tmp/furtka-build"
|
|
OUT_IN_CONTAINER="/work/iso/out"
|
|
|
|
rm -rf "$PROFILE_WORK" "$BUILD_WORK"
|
|
cp -a "$PROFILE_SRC" "$PROFILE_WORK"
|
|
|
|
echo "==> Overlaying Furtka customizations"
|
|
|
|
cat "$SCRIPT_DIR/overlay/packages.extra" >> "$PROFILE_WORK/packages.x86_64"
|
|
|
|
cat "$SCRIPT_DIR/overlay/profiledef.sh" >> "$PROFILE_WORK/profiledef.sh"
|
|
|
|
cp -a "$SCRIPT_DIR/overlay/airootfs/." "$PROFILE_WORK/airootfs/"
|
|
|
|
echo "==> Rebranding boot menu (GRUB + syslinux + systemd-boot)"
|
|
# releng ships menu entries labelled "Arch Linux install medium" across three
|
|
# bootloader configs (BIOS syslinux, GRUB, systemd-boot for UEFI). Rewrite to
|
|
# our brand. Done with sed (not a static overlay) so upstream archiso file
|
|
# moves don't silently leave stale Arch labels behind.
|
|
#
|
|
# Also rebrands the syslinux menu header ("MENU TITLE Arch Linux") and the
|
|
# per-entry HELP text shown at the bottom of the BIOS screen. GRUB/efiboot
|
|
# don't ship equivalent long descriptions, so menu-entry rename is enough there.
|
|
find "$PROFILE_WORK/grub" "$PROFILE_WORK/syslinux" "$PROFILE_WORK/efiboot" \
|
|
-type f \( -name "*.cfg" -o -name "*.conf" \) -print0 \
|
|
| xargs -0 sed -i \
|
|
-e 's/Arch Linux install medium/Furtka Live Installer/g' \
|
|
-e 's/Arch Linux live medium/Furtka Live Installer/g' \
|
|
-e 's/install Arch Linux or perform system maintenance/install Furtka or perform system maintenance/g' \
|
|
-e 's/^MENU TITLE Arch Linux$/MENU TITLE Furtka/'
|
|
|
|
# Mark the default entry as (Recommended) so first-time users know which to
|
|
# pick. Targets the main entry only — speech/accessibility variants stay
|
|
# unlabeled to avoid suggesting they're the normal choice.
|
|
sed -i 's/^title Furtka Live Installer (%ARCH%, UEFI)$/title (Recommended) Furtka Live Installer (%ARCH%, UEFI)/' \
|
|
"$PROFILE_WORK/efiboot/loader/entries/01-archiso-linux.conf"
|
|
sed -i 's/^MENU LABEL Furtka Live Installer (%ARCH%, BIOS)$/MENU LABEL (Recommended) Furtka Live Installer (%ARCH%, BIOS)/' \
|
|
"$PROFILE_WORK/syslinux/archiso_sys-linux.cfg"
|
|
sed -i "/--id 'archlinux'/s/menuentry \"Furtka Live Installer/menuentry \"(Recommended) Furtka Live Installer/" \
|
|
"$PROFILE_WORK/grub/grub.cfg" "$PROFILE_WORK/grub/loopback.cfg"
|
|
|
|
mkdir -p "$PROFILE_WORK/airootfs/opt/furtka"
|
|
cp -a "$REPO_ROOT/webinstaller/." "$PROFILE_WORK/airootfs/opt/furtka/"
|
|
# Ship the post-install asset tree (HTML, CSS, systemd units, scripts, …)
|
|
# next to webinstaller/app.py so _resolve_assets_dir() finds it at runtime.
|
|
cp -a "$REPO_ROOT/furtka/assets" "$PROFILE_WORK/airootfs/opt/furtka/assets"
|
|
rm -rf "$PROFILE_WORK/airootfs/opt/furtka/__pycache__"
|
|
|
|
# Pack the resource manager (furtka/ Python package + bundled apps/) as a
|
|
# tarball that webinstaller hands to archinstall via custom_commands. Lives at
|
|
# a fixed path in the live ISO; the installed system reads it back, untars
|
|
# into /opt/furtka/versions/<VERSION>/, and gets a working `furtka` CLI + the
|
|
# fileshare app. Same tarball shape as Phase-2 self-update releases, so an
|
|
# ISO-installed box and an updated box converge on the same layout.
|
|
echo "==> Bundling resource manager payload"
|
|
PAYLOAD_STAGE="$(mktemp -d)"
|
|
cp -a "$REPO_ROOT/furtka" "$PAYLOAD_STAGE/"
|
|
cp -a "$REPO_ROOT/apps" "$PAYLOAD_STAGE/"
|
|
find "$PAYLOAD_STAGE" -type d -name __pycache__ -exec rm -rf {} +
|
|
# VERSION at tarball root: the installer reads it to choose the versions/<ver>/
|
|
# directory name and /opt/furtka/current/VERSION reports it at runtime.
|
|
grep -E '^version = ' "$REPO_ROOT/pyproject.toml" | head -1 \
|
|
| sed 's/.*= "\(.*\)"/\1/' > "$PAYLOAD_STAGE/VERSION"
|
|
tar -czf "$PROFILE_WORK/airootfs/opt/furtka-resource-manager.tar.gz" \
|
|
-C "$PAYLOAD_STAGE" .
|
|
rm -rf "$PAYLOAD_STAGE"
|
|
|
|
mkdir -p "$PROFILE_WORK/airootfs/etc/systemd/system/avahi-daemon.service.d"
|
|
ln -sf /usr/lib/systemd/system/avahi-daemon.service \
|
|
"$PROFILE_WORK/airootfs/etc/systemd/system/multi-user.target.wants/avahi-daemon.service"
|
|
|
|
echo "==> Building ISO (mkarchiso)"
|
|
mkdir -p "$OUT_IN_CONTAINER"
|
|
mkarchiso -v -w "$BUILD_WORK" -o "$OUT_IN_CONTAINER" "$PROFILE_WORK"
|
|
|
|
echo
|
|
echo "==> Done. ISO(s) in $OUT_IN_CONTAINER (on host: iso/out/):"
|
|
ls -lh "$OUT_IN_CONTAINER"
|