28 docs tagged with "application"

What I am actively working on.

Includes start, finish and lap markers.

This section collects the applications I am the process of building, or ones already in production. They are local-first, run on-premises, and exist to solve real problems in my life. I share the work so it is reproducible and hopefully useful to others.

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.

2025-09-23

I explain the problem I am solving, who it is for, where this work fits within the wider documents, and what decisions and assumptions guide the plan.

Scoped to Stage 1 (foundation for personal coach – running data).

This document captures the major debugging sessions, errors, and fixes applied during development.

This document tracks major decisions made during development, why they were chosen, and alternatives considered.

Production-ready setup for self-hosted fitness tracking.

This section captures progress on the application, decisions taken, and fixes made along the way. It is where I track work in the open so I can repeat what works and avoid past mistakes.

Replace gitlab.reids.net.au with your server name.

Kubernetes notes for Stage 1.

1. Problem

Self-hosted application.

Purpose

Tracking progress across all stages.

Purpose

A small gallery of the fitness application running on an iPhone 14 Pro. These images are taken from my local-first build and show real screens from day-to-day use.

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.