Personal running data visualization app for activities managed by RunPaceFlow Admin.
- Read-only dashboard for running and cycling activities already stored in the activity database
- Map route visualization with animated playback
- Split pace analysis and charts
- Cached AI-powered running insights generated by RunPaceFlow Admin
- Lazy-loaded map components and optimized bundle size
- Runtime configuration loaded from RunPaceFlow Admin
- Responsive design for desktop and mobile
RunPaceFlow does not ingest or sync activity data directly. Data ingestion, third-party platform credentials, AI generation, PR Agent workflows, and runtime settings are managed by RunPaceFlow Admin. The main site calls Admin's read-only API, which reads the mounted shared.db; Turso is retained only as an Admin-side mirror/backup target.
Create a .env.local file:
# Required for the server-to-server read API (use the same token in Admin)
RUNPACEFLOW_ADMIN_URL=http://localhost:3030
RUNPACEFLOW_ADMIN_API_TOKEN=your_main_site_api_token
# Optional map style
NEXT_PUBLIC_MAP_STYLE=https://basemaps.cartocdn.com/gl/positron-gl-style/style.json
# AI credentials and model settings are configured in RunPaceFlow Admin.
# Goals (optional - customize weekly/monthly targets)
NEXT_PUBLIC_WEEKLY_DISTANCE_GOAL=10000
NEXT_PUBLIC_MONTHLY_DISTANCE_GOAL=50000
NEXT_PUBLIC_WEEKLY_DURATION_GOAL=3600
NEXT_PUBLIC_MONTHLY_DURATION_GOAL=18000RunPaceFlow Admin's scheduler generates personalized insights and stores them in
shared.db. The main site only reads the cached result; AI provider credentials
never need to be configured on the main site.
# Install dependencies
bun install
# Start dev server
bun run devVisit http://localhost:3000
Configure RUNPACEFLOW_ADMIN_URL and RUNPACEFLOW_ADMIN_API_TOKEN in the main-site deployment. Configure the same token as MAIN_SITE_API_TOKEN in Admin, and keep Turso's DATABASE_URL / DATABASE_AUTH_TOKEN only in Admin for its mirror job.
Inspired by yihong0618/running_page
MIT