homelab/documentation
Nathan 54a885120d feat(sparkyfitness): add sparkyfitness stack to heimdall
- Compose file with pinned images (v0.16.6.1), healthchecks, Traefik routing
- .env.example with all required variables and generation commands
- README covering access, appdata, backup scope, upgrade procedure
- KBA-002: deployment reference with verification and rollback steps
- repo-deploy.prompt.md: reusable end-to-end deployment workflow prompt
- Session snapshot 2026-05-10

Source: https://github.com/CodeWithCJ/SparkyFitness
2026-05-10 21:58:38 -04:00
..

Documentation

Overview

This directory contains all technical documentation for the Castaldi Family Homelab infrastructure.


Quick Reference

📘 Runbooks & Guides


Knowledge Base Articles (KBAs/)

Structured troubleshooting articles following the incident → resolution format.

GitOps & Deployment


Standard Operating Procedures (SOPs/)

Step-by-step guides for operational tasks and migrations.

Infrastructure Deployment

  • SOP-002: Initial Infrastructure Deployment
    Complete guide for deploying the homelab from scratch, including secure repository setup, Ansible control node configuration, core service deployment, and GitOps integration.

Stack Management


Document Conventions

  • KBA-XXX: Troubleshooting articles with clear problem/solution format (stored in KBAs/)
  • SOP-XXX: Procedural guides for operational tasks (stored in SOPs/)
  • Runbooks: Infrastructure reference and emergency procedures (root level)

Contributing

When documenting new issues or procedures:

  1. KBAs: Create in KBAs/ folder for troubleshooting scenarios with clear diagnosis → resolution
  2. SOPs: Create in SOPs/ folder for repeatable operational procedures and migrations
  3. Update Runbook: Add new emergency procedures to TECHNICAL_RUNBOOK.md
  4. Update Repository Memory: Store critical lessons in /memories/repo/
  5. Commit Messages: Use conventional commits (e.g., docs(kba): add KBA-002 for...)

Last Updated: April 12, 2026