Hey all, sharing what I've been working on. NutriTrace is a self-hosted nutrition and wellness tracker that runs entirely on your own server in a single Docker container.
I built it because every commercial nutrition app has the same shape. You hand them years of food data, body measurements, and biometrics, and your data is held hostage when they pivot or paywall. I wanted to track macros and pull in my Fitbit data without participating in that.
Daily food diary with multi-ingredient meals, recipes, body stats, water tracking, day-level notes. Personal food database, barcode scanner, imports from Open Food Facts and USDA, plus optional Mealie integration. Statistics with trend charts, full backup, exports as CSV / JSON / full ZIP.
Optional wellness device sync from Fitbit, Withings, Garmin, and Android Health Connect. Sleep / readiness / stress scores computed from your data.
Optional AI assistant where you bring your own Claude / OpenAI / Gemini key. It queries your real data via tool use so it can answer things like "what was my average protein this month" without making numbers up. There's a voice food logger too. Both fully optional, off by default.
Tech: Svelte 4 + Express + better-sqlite3, multi-stage Dockerfile, AGPL-3.0. Native Android app is in active development; PWA installs to home screen on any modern browser today.
Repo and docker-compose example: https://github.com/TraceApps/nutritrace
Happy to answer questions.
Thanks for the offers to help with translations. Wanted to share the plan.
I'm wiring up the translation infrastructure now: svelte-i18n with one JSON file per locale in the repo. The workflow once it's ready is straightforward. There'll be a single English source file at src/i18n/en.json, contributors copy it to their locale (fr.json, nl.json, de.json, etc.), translate the values, and open a pull request. Keys stay untouched, only values change.
Nothing to do right now. I'll open a GitHub tracking issue once the source file is stable enough to translate against. A short contributor guide will land with it covering workflow and conventions.
One thing worth flagging early: for nutrition labels specifically, please plan to use the regulatory terms that appear on food packaging in your country rather than the literal English equivalents. So Glucides / Lipides / Protéines for French, Koolhydraten / Vetten / Eiwitten for Dutch, Eiweiß rather than Protein for German, and so on.
More soon.
Quick update on this. Translation infrastructure is live as of v1.0.0-rc.6 (released today). The source file is
src/i18n/en.json— about 210 keys covering navigation, page titles, the full auth flow, the onboarding wizard, primary actions in Diary / Foods / Goals / Profile, the AI assistant FAB, and common toasts. Server-side strings (email subjects, push notification bodies) are out of scope for now.Full workflow is documented in
CONTRIBUTING.md → Translations.About 30% of the client-side surface is extracted in this batch — the screens every user touches every session. Wellness sync messages, deep Settings sub-section labels, and Statistics chart internals are the main gaps. If you hit a screen you use heavily that's still English while translating, open an issue listing the screen and I'll pull it forward in the next extraction batch.
Tag me on the PR when you're ready.