Self-hosted fitness tracker. Log workouts, track nutrition, and monitor progress. Docker deployment, mobile-friendly.
<!doctype html>
<html lang="en">
<head>
<meta charset="UTF-8" />
<link rel="icon" type="image/svg+xml" href="/favicon-transparent.svg" />
<link rel="icon" type="image/png" href="/favicon-transparent.png" />
<link rel="apple-touch-icon" href="/favicon-transparent.png" />
<meta name="viewport" content="width=device-width, initial-scale=1.0" />
<title>Lyftr — Workout & Nutrition Tracker</title>
<meta
name="description"
content="Log workouts, run guided gym sessions, and track nutrition and bodyweight. Self-hosted, so the data stays yours."
/>
<!--
surfaces.dark.base, matching the store's dark-first default — what the browser paints
before JS runs. applyThemeClass() then REPLACES this element on load and on every
toggle (see web/src/lib/lyftr.ts): browsers diff the value to decide whether to
repaint their chrome, and editing this element's content in place is not reliably
seen as a change.
Not a prefers-color-scheme pair, which is the usual advice: the theme comes from
localStorage and defaults to dark whatever the OS says, so a light-mode OS would paint
a light bar over a dark app.
-->
<meta name="theme-color" content="#070d1a" />
<!--
Every self-hosted instance ships this file, so a crawler that finds someone's server
would be indexing their private training log.
No og:* tags for the same reason: they need an absolute image URL, and the only one
available at build time is the project's CDN — so sharing a private instance in a chat
would tell that CDN the instance hostname. Links still preview from the title and
description above.
-->
<meta name="robots" content="noindex, nofollow" />
</head>
<body>
<div id="root"></div>
<script type="module" src="/src/main.tsx"></script>
</body>
</html>