Context
Self-hosted homelab and services platform used as a testbed, media stack, and operational workstation environment. Public site access could not be fully verified from this environment (private/internal resolution block), so externally visible status needs confirmation.
Goals
- Operate reliable self-hosted services for daily use.
- Maintain reproducible infrastructure and service lifecycle workflows.
- Continue consolidating service operations and observability.
Implementation
Stack
- Linux / Unix tooling
- Docker / Compose-based service operations
- Service mix includes media apps, Git hosting, reverse proxy, identity/secrets, and utilities
Architecture / Integrations
- Multi-service container platform with profile-based compose workflows
- Reverse proxy ingress + service-specific containers
- Legacy network topology is documented historically; some components are deprecated
Repos / URLs
- Domain: https://kuhree.com
- Source repo: https://git.kuhree.com/kuhree.com (no public GitHub repo)
- Planning note: planning
- Internal details: private
Status
Active. Many core services are marked operational in current inventory.
Next actionable milestone: reconcile service status table (✅/❌) against currently deployed stack and retire stale/dead entries.
Lessons
- Service sprawl grows quickly; maintain one canonical status inventory.
- Keep network diagrams current to reduce operational drift.
- Prefer explicit runbooks for pull/up/down/log/exec workflows.
Notes
- Existing command snippets remain useful for routine operations and should be retained in supporting docs.
- Sensitive host/network credentials and internal topology details should stay in private.