This section explains how the fitness application is structured, how it runs on-premises, and how the different services talk to each other. It also links to the deployment, Kubernetes, and webhook details so I can come back later and repeat the setup.
Scoped to Stage 1 (foundation for personal coach – running data).
Production-ready setup for self-hosted fitness tracking.
Cluster data store overview, checks, and impact.
Kubernetes notes for Stage 1.
OAuth setup, email via Graph API, security hardening, first login, and troubleshooting for the Cal.com scheduling stack.
Azure App Registration, smtp2graph configuration, Prometheus metrics, and troubleshooting.
Post-deployment setup, testing alerts, and troubleshooting for the observability stack.
This document describes the complete webhook implementation for real-time Strava activity notifications.
High-level services and how they communicate.
Short context of the stack and why I chose it. Scope: Stage 1.