Architecture

How Dinatos is built and why, for people changing the code. If you only want to run it, see Running your own instance; to use it, see Using Dinatos.

Dinatos is a self-hosted workout tracker: a FastAPI backend with a Postgres database, and a Flutter app (web and Android) that talks to it over REST.

Suggested reading order:

1. Domain model: the terms and repository layout.

2. Backend: API, auth, backup, imports.

3. Frontend: the Flutter app.

4. Distribution: how releases are packaged.

Operational gotchas for building and testing live in AGENTS.md and CONTRIBUTING.md at the repository root.

• Domain model and repository layout
  • Concepts
  • Repository layout
  • Module boundaries
• Backend
  • API surface
  • API documentation
  • Authentication
  • API keys
  • Backup and data export
  • Calendar feed
  • MCP server
  • Hevy import
  • Intervals.icu import
  • Exercise tutorials
  • Container image
• Frontend
  • Overview
  • Authentication
  • Server URL
  • Secure storage can throw
  • Insecure-TLS toggle
  • CORS on the web target
  • First-run tour
  • Routines and activities share an editor shape
  • Supersets
  • Live workout
  • Planned workouts and reminders
  • “Which athlete do you resemble?”
• Distribution
  • What a release produces
  • The Docker image builds its own frontend
  • Android APK signing
  • Building locally
  • Linux desktop target