2026-07-05 — Sepia Phase1 Core Compose Hardening
Summary
Completed the first core batch of Sepia Phase 1 infrastructure hardening across the main compose services.
Context
This work is part of the active Sepia infrastructure hardening plan, which must run before the later container update, DNS migration, and compose/networking polish plans.
Changes
Change 1: Hardened the core services
- Files:
/opt/compose.dsmr.yaml/opt/compose.esphome.yaml/opt/compose.grafana.yaml/opt/compose.homeassistant.yaml/opt/compose.influxdb.yaml/opt/compose.seafile.yaml/opt/compose.timescaledb.yaml- What: Added healthchecks, dependency health gates where appropriate, capability drops where safe, and basic resource limits.
Change 2: Verified the compose model
- Files:
/opt/compose.yamland the included service files above - What: Ran
docker compose configafter the edits to confirm the merged stack still validates.
Decisions
- Kept the first phase-1 commit limited to the core compose services instead of trying to force the entire hardening plan in one go.
- Deferred collectd and the Dockerfile hygiene work to the next step so this batch could be verified and committed cleanly.
Issues Encountered
- Earlier broader YAML edits failed validation, so the batch was rebuilt and verified in a narrower form.
Next Steps
- Finish the remaining Phase 1 items, especially collectd and the Dockerfile hygiene work.
- Continue to Phase 2 updates once Phase 1 is complete.
Generated: 2026-07-05