Migration nach llmnode #60

Merged
Lars merged 5 commits from develop into main 2026-10-29 15:53:42 +01:00
5 Commits
Author SHA1 Message Date
LarsandClaude Opus 5.5 36d51d4c33 Deploy production to llm-node alongside the Pi.
Deploy Development / deploy (push) Successful in 55s
Test Suite / pytest-backend (push) Successful in 51s
Test Suite / lint-backend (push) Successful in 0s
Test Suite / build-frontend (push) Successful in 17s
Test Suite / k6 /health Baseline (push) Successful in 35s
Test Suite / playwright-tests (push) Failing after 7m46s
A separate workflow on the linux_host runner deploys main to llm-node with its own checkout, /etc/shinkan/prod.env and a compose override that mounts the NAS media without creating host paths. Media retention stays off there until it is explicitly enabled, because both installations share the media pool. The deploy only passes when /api/health/ready reports a ready database and complete schema. The Pi workflow keeps its name and label and now aborts on any other host.

Also documents both deployments and the recovery contract with the backup orchestrator.

version: 0.8.246 (backend)

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-29 15:47:38 +01:00
LarsandCursor ad7c7ad4e5 Keep the dev deploy and the test suite as separate workflows.
Deploy Development / deploy (push) Successful in 59s
Test Suite / pytest-backend (push) Successful in 49s
Test Suite / lint-backend (push) Successful in 0s
Test Suite / build-frontend (push) Successful in 16s
Test Suite / k6 /health Baseline (push) Successful in 43s
Test Suite / playwright-tests (push) Failing after 7m54s
Tests no longer run as jobs inside the development deploy. A push to develop starts the test suite on its own and aims it at the dev stack.

Co-authored-by: Cursor <cursoragent@cursor.com>
2026-10-28 13:54:42 +01:00
LarsandCursor 5fc839afbc Run develop tests after the dev deploy, never against production by default.
Deploy Dev Stack / deploy (push) Successful in 55s
Deploy Dev Stack / pytest-backend (push) Successful in 50s
Deploy Dev Stack / lint-backend (push) Successful in 0s
Deploy Dev Stack / build-frontend (push) Successful in 17s
Deploy Dev Stack / k6 /health Baseline (push) Successful in 32s
Deploy Dev Stack / playwright-tests (push) Failing after 7m48s
workflow_run uses the workflow file on main and fell through to the prod directory when the triggering name was missing. Dev checks now follow Deploy Dev Stack and target the dev stack explicitly.

Co-authored-by: Cursor <cursoragent@cursor.com>
2026-10-28 13:34:33 +01:00
LarsandCursor d4a193607f Run the dev test suite once, after the deploy.
Deploy Development / deploy (push) Successful in 54s
The compose check looked for docker-compose.yml inside the backend image, where that file is not copied. A push no longer starts a second suite in parallel with the deploy.

Co-authored-by: Cursor <cursoragent@cursor.com>
2026-10-28 11:36:56 +01:00
LarsandCursor 95d365d9fa Schedule media retention at 03:00 Europe/Berlin.
Deploy Development / deploy (push) Successful in 1m1s
Test Suite / pytest-backend (push) Failing after 49s
Test Suite / lint-backend (push) Successful in 1s
Test Suite / build-frontend (push) Successful in 19s
Test Suite / k6 /health Baseline (push) Successful in 35s
Test Suite / playwright-tests (push) Failing after 7m57s
The folded python -c command crashed the cron container before any run. Content-report rate limiting now applies only after the good-faith declaration.

Co-authored-by: Cursor <cursoragent@cursor.com>
2026-10-28 11:14:37 +01:00