a1a57b04bb
Serwisy o jednorodnej tresci (bez wydzielonej sekcji deploy/runbook): kb-postgres, stability-agent, llm-gateway, vikunja, zigbee2mqtt, npm, forgejo, ollama, ir-ac-ha-integration, chelsty-stability-agent. Deprecated: mosquitto (NOT DEPLOYED/LEGACY), home-assistant-ken-legacy (archiwum importu), joplin (stub z 2026-04-15, brak katalogu services/joplin/). git mv + frontmatter, tresc nietknieta. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
33 lines
1.2 KiB
Markdown
33 lines
1.2 KiB
Markdown
---
|
|
okf: "0.1"
|
|
type: service
|
|
visibility: private
|
|
status: deprecated
|
|
updated: 2026-07-22
|
|
links: []
|
|
superseded_by: "kb/services/home-assistant.md — instancja ken (HAOS na RPi4), archiwum importu 2026-07-22"
|
|
---
|
|
|
|
# ken-legacy — historical archive, do not deploy
|
|
|
|
This directory holds the `/config` import of the **pre-migration** Home
|
|
Assistant instance: the `homeassistant5` container on piha, wound down
|
|
2026-07. It is kept for historical reference only — e.g. recovering the
|
|
logic of an old automation — not as a live or deployable instance.
|
|
|
|
See `services/home-assistant/DESIGN.md`, "Incident log" (2026-07-22) for
|
|
why this instance exists separately from the canonical `ken` (now the
|
|
Home Assistant OS instance on the RPi4 at 192.168.31.7): this container
|
|
kept running after the real migration and was firing automations in
|
|
parallel with the real home instance until the cutover was caught and
|
|
fixed.
|
|
|
|
**Rules for humans and agents:**
|
|
- Never run `import.sh ken-legacy` expecting a deploy target — it isn't
|
|
one. `services/home-assistant/instances.yaml` marks it `status:
|
|
archived` for this reason.
|
|
- Never write back to `homeassistant5` from this directory.
|
|
- Treat everything here as read-only history.
|
|
|
|
Archival import performed: 2026-07-22.
|