- Rewrite AGENTS.md: DB as source of truth, MCP knowledge tools, archive refs - Fix OIKOS.md: seeds/ paths, remove Python-era notes, update deployment status - Fix commands.md, agent-enrollment.md: archive/knowledge/ links - Fix all SKILL.md files: remove hosts/*.yaml refs, point to inventory.yaml - Fix HERMES.md, schema.md, page-templates.md, llm-wiki.md: update paths - Fix bootstrap.sh: identity check reads inventory.yaml - Fix README.md, cutover-checklist.md: stale wiki references - Move convert-wiki.py to archive/ (one-shot done)
1.5 KiB
1.5 KiB
name, risk_class, inputs, verification, docs_update_checklist
| name | risk_class | inputs | verification | docs_update_checklist | ||||
|---|---|---|---|---|---|---|---|---|
| config-change-deploy | config_mutation |
|
curl -sf <service_url> (or homelab service <name> health) |
|
Config change + deploy
Goal: change a tracked config repo (Caddy, Gitea customizations, an app's own repo) and get it live, safely.
homelab change preflight <service>— current health, the service'sconfig_repo, its risk class, and the verification command to run after. If risk class requires approval (config_mutationordestructive), stop and get operator sign-off before editing — seeseeds/policy.yaml.- Clone/pull the
config_repo(never edit the backend's working tree directly — tracked configs change by commit + push, per OIKOS.md conventions). - Make the change, commit, push to
main. - The Gitea webhook fires the deploy pipeline for that repo (see infrastructure/auto-deploy.md for the exact receiver/reload for this service).
- Run the preflight's verification command. If it fails, check
homelab service <name> logfor the reload/restart error. - Record the change: once
oikos/ledger.pyis wired into deploy tooling (Week 3), this is automatic; until then, note the change and outcome in the relevant investigation/plan doc.
Docs-update checklist: update the service's doc_page if the change
alters its behavior, ingress route, or ownership; add a changelog entry
if the page has one.