2 Commits
Author SHA1 Message Date
LarsandClaude Opus 5.5 1bdb039a91 ci: Cutover auf llm-node, Pi-Deploy nur noch manuell
Deploy Development / deploy (push) Successful in 1m0s
Test Suite / pytest-backend (push) Successful in 50s
Test Suite / lint-backend (push) Successful in 0s
Test Suite / build-frontend (push) Successful in 16s
Test Suite / k6 /health Baseline (push) Successful in 35s
Test Suite / playwright-tests (push) Failing after 7m53s
- deploy-prod.yml (Pi): Trigger nur noch workflow_dispatch, kein Lauf bei Push auf main
- deploy-prod-llm-node.yml: MEDIA_RETENTION enabled, retention-cron läuft auf llm-node
- test.yml: kein workflow_run nach Deploy Production mehr, nur develop gegen Dev
- PROD_DEPLOYMENTS.md, CLAUDE.md: llm-node als einzige Prod, Rückfallweg Pi

version: 0.8.247 (backend)

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-29 18:48:30 +01:00
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