4 Commits

Include renames

Author	SHA1	Message	Date
franzz	9a5f2ac639	Swaping back to nodejs dependent checkout	2026-09-14 23:58:53 +02:00
franzz	a7a8ab6f4e	Simplify deployment	2026-09-14 23:48:51 +02:00
franzzandClaude Opus 5	4cff820070	Check out with git rather than actions/checkout ... actions/checkout is a JavaScript action, so a host-mode runner needs node on its PATH to run it and fails with "Cannot find: node in PATH" without one. Every step is plain shell now, which needs nothing of the runner beyond git, python3, rsync and curl. The clone is shallow and takes its URL from the live checkout's remote, so there is no URL or token in the workflow. It works because the runner already has to run as the user that owns that checkout. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>	2026-09-14 23:35:29 +02:00
franzzandClaude Opus 5	467cae4dd5	Add a Gitea deploy workflow and the systemd unit it restarts ... Shaped after the Livetrail workflow: one job on a project-labelled host runner, preflight checks, rsync from the runner's checkout. rsync rather than a pull in the live directory, so the deploy needs no credentials of its own for git:. The tests run first and gate the rest, .venv and members.json are excluded so the runtime and the learned stereo pair survive, and the last step waits for the panel to answer -- the home page renders from config alone, so it says the app came back up without waiting on the speakers. The unit carries the real paths and user, which the README's sketch of it never did. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>	2026-09-14 22:56:21 +02:00